Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d350eaf2f0ebe2b6c7c464177c568f8e86212ca939f1b135d9357289a17fadb

Tx prefix hash: 5837634292665ef40b9ac681b29551a364be32662fa60d1a82dce990d21223ba
Tx public key: e75092e3aa5fbb9eeb7b724a6fb52347c2c6bcf69886705f00a3c0ba59be9362
Timestamp: 1737676657 Timestamp [UCT]: 2025-01-23 23:57:37 Age [y:d:h:m:s]: 00:292:21:07:36
Block: 1203907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206857 RingCT/type: yes/0
Extra: 01e75092e3aa5fbb9eeb7b724a6fb52347c2c6bcf69886705f00a3c0ba59be93620211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2d4a5240e2aa5ffcd7d3cd988810b8b5d6232c6d0eb6becc23364359f46444e 0.600000000000 1690588 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": 1203917, "vin": [ { "gen": { "height": 1203907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2d4a5240e2aa5ffcd7d3cd988810b8b5d6232c6d0eb6becc23364359f46444e" } } ], "extra": [ 1, 231, 80, 146, 227, 170, 95, 187, 158, 235, 123, 114, 74, 111, 181, 35, 71, 194, 198, 188, 246, 152, 134, 112, 95, 0, 163, 192, 186, 89, 190, 147, 98, 2, 17, 0, 0, 0, 7, 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