Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85ba2aa16156612b2d5ff96f28952c32c5a68bfed00386bd48db0745e3421006

Tx prefix hash: f10b7009ff16a89d70f3e6623aa3895bf46dc5fb24b6efe1edd324a195bffc45
Tx public key: e236c90b590bfa3835f4a7973a0e9b8df3a5b009958b7014891f9786c7b1cd51
Timestamp: 1704807506 Timestamp [UCT]: 2024-01-09 13:38:26 Age [y:d:h:m:s]: 00:319:20:59:58
Block: 931595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229032 RingCT/type: yes/0
Extra: 01e236c90b590bfa3835f4a7973a0e9b8df3a5b009958b7014891f9786c7b1cd510211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ae152d669c7f75739217241a3d00616e6755cbe0291bb810d5685f9f7a711c7 0.600000000000 1389499 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": 931605, "vin": [ { "gen": { "height": 931595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ae152d669c7f75739217241a3d00616e6755cbe0291bb810d5685f9f7a711c7" } } ], "extra": [ 1, 226, 54, 201, 11, 89, 11, 250, 56, 53, 244, 167, 151, 58, 14, 155, 141, 243, 165, 176, 9, 149, 139, 112, 20, 137, 31, 151, 134, 199, 177, 205, 81, 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