Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e381447036a1829b071f1363678d63aceb04de77ac684bfb64b7e7f17786e5

Tx prefix hash: 04368579f940f154e7a86c24cbae630c69ba9caf853af59ec140899505780fcc
Tx public key: 0cb11789b1d441c90d9e5bb20e8f020ebd4bd75c22c13c20b5c430696c507a74
Timestamp: 1717884419 Timestamp [UCT]: 2024-06-08 22:06:59 Age [y:d:h:m:s]: 01:158:10:43:31
Block: 1040018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371820 RingCT/type: yes/0
Extra: 010cb11789b1d441c90d9e5bb20e8f020ebd4bd75c22c13c20b5c430696c507a7402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bd83f9ab1141f48cda891b8f4b34b1a82beb9667299b562a6fc981262a3b1c2 0.600000000000 1508673 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": 1040028, "vin": [ { "gen": { "height": 1040018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bd83f9ab1141f48cda891b8f4b34b1a82beb9667299b562a6fc981262a3b1c2" } } ], "extra": [ 1, 12, 177, 23, 137, 177, 212, 65, 201, 13, 158, 91, 178, 14, 143, 2, 14, 189, 75, 215, 92, 34, 193, 60, 32, 181, 196, 48, 105, 108, 80, 122, 116, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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