Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970b1f3ef7a7acd3d23349d951010abeefd2c816b0d17d99f444e5bd278d3e42

Tx prefix hash: 51f8fbfa637aa3ae71b37516583d971107fd256e03a3a725b937b6e89b505d9d
Tx public key: 202bd4cf6cd5875250e8783a0c3469c87f55f56d97dabfc6a3dc654993cae4a2
Timestamp: 1715060116 Timestamp [UCT]: 2024-05-07 05:35:16 Age [y:d:h:m:s]: 00:234:09:38:45
Block: 1016605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167764 RingCT/type: yes/0
Extra: 01202bd4cf6cd5875250e8783a0c3469c87f55f56d97dabfc6a3dc654993cae4a202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39c131f2b8699dd68f4b6cfe1391d1d376a32df9106fffc66170d699d8a52fd4 0.600000000000 1480236 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": 1016615, "vin": [ { "gen": { "height": 1016605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39c131f2b8699dd68f4b6cfe1391d1d376a32df9106fffc66170d699d8a52fd4" } } ], "extra": [ 1, 32, 43, 212, 207, 108, 213, 135, 82, 80, 232, 120, 58, 12, 52, 105, 200, 127, 85, 245, 109, 151, 218, 191, 198, 163, 220, 101, 73, 147, 202, 228, 162, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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