Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c35f2ab2e4e7430e7d9ba91b4212542d6fe0d27f30c389116f7d7d8ca0ddcbaf

Tx prefix hash: 1431f5481a8e900d6d2c4dc8e81a48e875462e8688625ddc7b6c163a721c3a4d
Tx public key: 8c11bc32e14dcc5946317b9611fc4b9476cbdb789462a0b3d4ac7382b68aeed8
Timestamp: 1710202213 Timestamp [UCT]: 2024-03-12 00:10:13 Age [y:d:h:m:s]: 01:032:05:57:49
Block: 976339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284029 RingCT/type: yes/0
Extra: 018c11bc32e14dcc5946317b9611fc4b9476cbdb789462a0b3d4ac7382b68aeed80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da51d3ee1e28f36fe5bef8565c80b247bcedf2120d09974f6887fd4e60844234 0.600000000000 1436332 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": 976349, "vin": [ { "gen": { "height": 976339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da51d3ee1e28f36fe5bef8565c80b247bcedf2120d09974f6887fd4e60844234" } } ], "extra": [ 1, 140, 17, 188, 50, 225, 77, 204, 89, 70, 49, 123, 150, 17, 252, 75, 148, 118, 203, 219, 120, 148, 98, 160, 179, 212, 172, 115, 130, 182, 138, 238, 216, 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