Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bd2e1756d8b404cbcd02b30aa4a1f75e9b541f9052ff7d580950e58e618c688c

Tx prefix hash: f3cdd80b4a0f8a191aa0d708943df5bd93662882dbdd09068bd6cbbb2f0a5fde
Tx public key: 2fc317349dc348b80b5f701b255b986a50ec703c1859b9ed035033d059c12830
Timestamp: 1702374862 Timestamp [UCT]: 2023-12-12 09:54:22 Age [y:d:h:m:s]: 01:118:22:14:09
Block: 911451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346120 RingCT/type: yes/0
Extra: 012fc317349dc348b80b5f701b255b986a50ec703c1859b9ed035033d059c1283002110000000c33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72e6abbb5ecd92aa75f6f94dc4e34bbcb307a643d4e8e27d7a8ea85d6aee070d 0.600000000000 1368655 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 911461, "vin": [ { "gen": { "height": 911451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72e6abbb5ecd92aa75f6f94dc4e34bbcb307a643d4e8e27d7a8ea85d6aee070d" } } ], "extra": [ 1, 47, 195, 23, 52, 157, 195, 72, 184, 11, 95, 112, 27, 37, 91, 152, 106, 80, 236, 112, 60, 24, 89, 185, 237, 3, 80, 51, 208, 89, 193, 40, 48, 2, 17, 0, 0, 0, 12, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8