Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b9a1c5fffe57f6226b5501302400e58d573a33fa3d210bb6018cc177d4e6ce9

Tx prefix hash: 72b0b49fcd47d13ef5c05a760cc23d91518d10e0a7db343f761442d033d43432
Tx public key: 368fe5349c742c410f7d8e95ae99edf190f2380aae3a685cb07fe6e14a3b0f00
Timestamp: 1714728183 Timestamp [UCT]: 2024-05-03 09:23:03 Age [y:d:h:m:s]: 00:318:02:51:06
Block: 1013851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227413 RingCT/type: yes/0
Extra: 01368fe5349c742c410f7d8e95ae99edf190f2380aae3a685cb07fe6e14a3b0f000211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f6b6f2fa641494ce43b24d9459bd8a38aae1b946ee677adb853591ddaa9d97c 0.600000000000 1476778 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": 1013861, "vin": [ { "gen": { "height": 1013851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f6b6f2fa641494ce43b24d9459bd8a38aae1b946ee677adb853591ddaa9d97c" } } ], "extra": [ 1, 54, 143, 229, 52, 156, 116, 44, 65, 15, 125, 142, 149, 174, 153, 237, 241, 144, 242, 56, 10, 174, 58, 104, 92, 176, 127, 230, 225, 74, 59, 15, 0, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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