Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 180820270ee026b14645dc4d9a9262a275876277d28e57de5d55ce3e0c6a880c

Tx prefix hash: 4529297e56c8e7dd2d0b17436023a15d5d2801e30c634bc91f0eaeb3e577aeca
Tx public key: 97f98fc1902f9a14ea0b2cc7d3a320ef4df3be620d4ce56dcee132463bf176c7
Timestamp: 1712746267 Timestamp [UCT]: 2024-04-10 10:51:07 Age [y:d:h:m:s]: 01:048:16:57:05
Block: 997400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295819 RingCT/type: yes/0
Extra: 0197f98fc1902f9a14ea0b2cc7d3a320ef4df3be620d4ce56dcee132463bf176c70211000000130011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f449a9d46452cd0f84823e9d42dfcf768b2350165e97bfc72ed95d4f01e4a81d 0.600000000000 1457832 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": 997410, "vin": [ { "gen": { "height": 997400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f449a9d46452cd0f84823e9d42dfcf768b2350165e97bfc72ed95d4f01e4a81d" } } ], "extra": [ 1, 151, 249, 143, 193, 144, 47, 154, 20, 234, 11, 44, 199, 211, 163, 32, 239, 77, 243, 190, 98, 13, 76, 229, 109, 206, 225, 50, 70, 59, 241, 118, 199, 2, 17, 0, 0, 0, 19, 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