Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df8f6145a13bd4b14818de88eb2085c3af62f181431109e1eee4153f4eb11500

Tx prefix hash: 0d6f16c84f8a5b2f3dece6ec070e73dfc486d7115505a0c4794ec5eeb666feee
Tx public key: d10d6c8573f004472186cc0f16f5ed3a7a66cfed71f6b78ef8190e37b2e44e70
Timestamp: 1730023450 Timestamp [UCT]: 2024-10-27 10:04:10 Age [y:d:h:m:s]: 00:155:01:21:57
Block: 1140620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110611 RingCT/type: yes/0
Extra: 01d10d6c8573f004472186cc0f16f5ed3a7a66cfed71f6b78ef8190e37b2e44e70021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f58e9b8d8a7af1ec4887094a7dbbb1d3a2ce42496f8865c884196dbfda6ac40e 0.600000000000 1624421 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": 1140630, "vin": [ { "gen": { "height": 1140620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f58e9b8d8a7af1ec4887094a7dbbb1d3a2ce42496f8865c884196dbfda6ac40e" } } ], "extra": [ 1, 209, 13, 108, 133, 115, 240, 4, 71, 33, 134, 204, 15, 22, 245, 237, 58, 122, 102, 207, 237, 113, 246, 183, 142, 248, 25, 14, 55, 178, 228, 78, 112, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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