Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64b5e9414e527cd9c4a9f4f413f3beb538b3f027dae3c479c01fb226dcf98d83

Tx prefix hash: 357216764c38c975634e1339315fce9a31dfcce96891806d865deb8f80f8880f
Tx public key: c3115bc5c1cbe2b10124a62963516fe794c86941ed32530d5a2c1bc0b4cbffe7
Timestamp: 1715484969 Timestamp [UCT]: 2024-05-12 03:36:09 Age [y:d:h:m:s]: 00:329:22:05:19
Block: 1020156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235779 RingCT/type: yes/0
Extra: 01c3115bc5c1cbe2b10124a62963516fe794c86941ed32530d5a2c1bc0b4cbffe702110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20f77416542a61ae5af1a3bb88c401fb99eec61fab1f18535908b5bfa49c5570 0.600000000000 1484215 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": 1020166, "vin": [ { "gen": { "height": 1020156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20f77416542a61ae5af1a3bb88c401fb99eec61fab1f18535908b5bfa49c5570" } } ], "extra": [ 1, 195, 17, 91, 197, 193, 203, 226, 177, 1, 36, 166, 41, 99, 81, 111, 231, 148, 200, 105, 65, 237, 50, 83, 13, 90, 44, 27, 192, 180, 203, 255, 231, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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