Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7cae17b0a72fca54cc6d784f5ee3e0fa825eb509c5f081f43a26896cd07b156

Tx prefix hash: 5f47ec44b53ced351fc937030db0e05560a91476ef96cc296cd472399eb37341
Tx public key: 0a193eb64c2233eeb18da4b14d41f3b96abc37b6f188dc537fbc9dc9a73620da
Timestamp: 1732140493 Timestamp [UCT]: 2024-11-20 22:08:13 Age [y:d:h:m:s]: 00:348:04:19:30
Block: 1158105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246374 RingCT/type: yes/0
Extra: 010a193eb64c2233eeb18da4b14d41f3b96abc37b6f188dc537fbc9dc9a73620da0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da466317b0a5f8df6da6dd07fca661d5a8bd59182464bd1147123d46ab873d8c 0.600000000000 1643734 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": 1158115, "vin": [ { "gen": { "height": 1158105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da466317b0a5f8df6da6dd07fca661d5a8bd59182464bd1147123d46ab873d8c" } } ], "extra": [ 1, 10, 25, 62, 182, 76, 34, 51, 238, 177, 141, 164, 177, 77, 65, 243, 185, 106, 188, 55, 182, 241, 136, 220, 83, 127, 188, 157, 201, 167, 54, 32, 218, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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