Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8af83db072b37fa51c04fe7a42c33a516d7c72de978816c3c214a4f2a25977ff

Tx prefix hash: 60576f071922a48f255869ed0b0fc65471e6b3c0a1d3af784e1ce4c35b478274
Tx public key: 01a0437c61e2d49c18a0f7009a0151a766164fe18ddaea80e107db3152d06eb5
Timestamp: 1717138411 Timestamp [UCT]: 2024-05-31 06:53:31 Age [y:d:h:m:s]: 00:307:08:02:05
Block: 1033834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219642 RingCT/type: yes/0
Extra: 0101a0437c61e2d49c18a0f7009a0151a766164fe18ddaea80e107db3152d06eb50211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d68f53af7fc457a2e0a0a12f1cd72f2b763d9492d4dc0c1f222b28b43af10a2 0.600000000000 1502307 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": 1033844, "vin": [ { "gen": { "height": 1033834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d68f53af7fc457a2e0a0a12f1cd72f2b763d9492d4dc0c1f222b28b43af10a2" } } ], "extra": [ 1, 1, 160, 67, 124, 97, 226, 212, 156, 24, 160, 247, 0, 154, 1, 81, 167, 102, 22, 79, 225, 141, 218, 234, 128, 225, 7, 219, 49, 82, 208, 110, 181, 2, 17, 0, 0, 0, 2, 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