Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6003fb0ca3addb1ed361ae47b728800817cde02fe778ed2ce0a7f7e620735d54

Tx prefix hash: 68b8c2b498b5a8842503cbd65e2d64eb1f14e7ad415bd44aaf71dcb0891ac3b4
Tx public key: 877029fcb3b617c7a113e38e9f30c455740596df26c6bb7c2a8f369036e12e24
Timestamp: 1722288759 Timestamp [UCT]: 2024-07-29 21:32:39 Age [y:d:h:m:s]: 00:167:04:09:48
Block: 1076519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119613 RingCT/type: yes/0
Extra: 01877029fcb3b617c7a113e38e9f30c455740596df26c6bb7c2a8f369036e12e2402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc9af15db170f7415a85957af840952a0f1a9650123cd678485fb29ced3f41fc 0.600000000000 1549056 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": 1076529, "vin": [ { "gen": { "height": 1076519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc9af15db170f7415a85957af840952a0f1a9650123cd678485fb29ced3f41fc" } } ], "extra": [ 1, 135, 112, 41, 252, 179, 182, 23, 199, 161, 19, 227, 142, 159, 48, 196, 85, 116, 5, 150, 223, 38, 198, 187, 124, 42, 143, 54, 144, 54, 225, 46, 36, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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