Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4c60449085cd694bb8c15a572c9fe557dca8e421a298f87e9e7daa237d7b61a

Tx prefix hash: 8682106bd070c9c76f129dba3223c3cb9c2f38d7c299787cddac5d1323cb7f4f
Tx public key: 4164c3aea4c70ade60d4fa6d75391cbcdbe37d7c7a4b6f89578edfba385ce3b3
Timestamp: 1700836083 Timestamp [UCT]: 2023-11-24 14:28:03 Age [y:d:h:m:s]: 01:145:01:46:33
Block: 898672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364857 RingCT/type: yes/0
Extra: 014164c3aea4c70ade60d4fa6d75391cbcdbe37d7c7a4b6f89578edfba385ce3b302110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.646139949000 dcy

stealth address amount amount idx
00: 0264e689235ae3aa52771c0da6b11d8df041a035cebe2454fd31a20470a0a16a 0.646139949000 1355101 of 0

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": 898682, "vin": [ { "gen": { "height": 898672 } } ], "vout": [ { "amount": 646139949, "target": { "key": "0264e689235ae3aa52771c0da6b11d8df041a035cebe2454fd31a20470a0a16a" } } ], "extra": [ 1, 65, 100, 195, 174, 164, 199, 10, 222, 96, 212, 250, 109, 117, 57, 28, 188, 219, 227, 125, 124, 122, 75, 111, 137, 87, 142, 223, 186, 56, 92, 227, 179, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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