Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33952e54edb9a3269807856c7063409b955eec2dcf45a6f8a7d6cd033fb33b13

Tx prefix hash: 7eed5ccc177227cf9916a9a773c78b9f675416f6a5a2e8543efa8fb78dd499f0
Tx public key: 056f30c5971534d1ccc8749c8cb30c03ea4a76b4150f87276ae4ffd40a87da23
Timestamp: 1701664630 Timestamp [UCT]: 2023-12-04 04:37:10 Age [y:d:h:m:s]: 01:047:04:29:53
Block: 905535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295077 RingCT/type: yes/0
Extra: 01056f30c5971534d1ccc8749c8cb30c03ea4a76b4150f87276ae4ffd40a87da2302110000000675e3f0e9000000000000000000

1 output(s) for total of 0.613178071000 dcy

stealth address amount amount idx
00: cdfe5937a226394e0f37127434dc8044831dbf9486fd6b2c9479d4503387f1f0 0.613178071000 1362424 of 0

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": 905545, "vin": [ { "gen": { "height": 905535 } } ], "vout": [ { "amount": 613178071, "target": { "key": "cdfe5937a226394e0f37127434dc8044831dbf9486fd6b2c9479d4503387f1f0" } } ], "extra": [ 1, 5, 111, 48, 197, 151, 21, 52, 209, 204, 200, 116, 156, 140, 179, 12, 3, 234, 74, 118, 180, 21, 15, 135, 39, 106, 228, 255, 212, 10, 135, 218, 35, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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