Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a59a04c56c6c82acd0114277ee0c5ed24be364cfc957d61630756196de7b57d

Tx prefix hash: 62bd2748fbd7b4ab1602f9c3e41cffd0130e88f2c3fdbf3d9893e5545adfa1b2
Tx public key: 2e22d1fb583e0c000c3e435ef4e41004ca917bd3dffab2f3f6a91656346280a8
Timestamp: 1712869199 Timestamp [UCT]: 2024-04-11 20:59:59 Age [y:d:h:m:s]: 00:353:22:40:55
Block: 998416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253062 RingCT/type: yes/0
Extra: 012e22d1fb583e0c000c3e435ef4e41004ca917bd3dffab2f3f6a91656346280a80211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5987253c084c9ddd2bfc84e8dd0fad6d7c322214b370aec1c0f9c33b410712c2 0.600000000000 1458866 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": 998426, "vin": [ { "gen": { "height": 998416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5987253c084c9ddd2bfc84e8dd0fad6d7c322214b370aec1c0f9c33b410712c2" } } ], "extra": [ 1, 46, 34, 209, 251, 88, 62, 12, 0, 12, 62, 67, 94, 244, 228, 16, 4, 202, 145, 123, 211, 223, 250, 178, 243, 246, 169, 22, 86, 52, 98, 128, 168, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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