Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94f0f581dc2dbdea194fcf357f533b04a97ea5b855d92105ee3174494757dcaa

Tx prefix hash: c6b352e2fad3a828b5a3227de8d2276a9a5aedf7d12a33ccc93e4074c891b39c
Tx public key: 0f39902fab33637ee11e57383db5828d024b8ccd28a02b7037f6b749e006ea7c
Timestamp: 1718844162 Timestamp [UCT]: 2024-06-20 00:42:42 Age [y:d:h:m:s]: 00:186:04:18:31
Block: 1047969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133274 RingCT/type: yes/0
Extra: 010f39902fab33637ee11e57383db5828d024b8ccd28a02b7037f6b749e006ea7c0211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4456c25f4b99eb2155780f424500c63fed6d832ab47c2338dc8cabb18feba972 0.600000000000 1517932 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": 1047979, "vin": [ { "gen": { "height": 1047969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4456c25f4b99eb2155780f424500c63fed6d832ab47c2338dc8cabb18feba972" } } ], "extra": [ 1, 15, 57, 144, 47, 171, 51, 99, 126, 225, 30, 87, 56, 61, 181, 130, 141, 2, 75, 140, 205, 40, 160, 43, 112, 55, 246, 183, 73, 224, 6, 234, 124, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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