Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549e068ec6c198ec827e10d40401df20615cb3359950210493922ac838ff50b9

Tx prefix hash: 20fb31054c8fc626a1c753597f38a2b1f308219a66f28fe0fcf0079ecd809f14
Tx public key: d4cdc2f61ec5f042f920d3f7d3b78dad1fba064e2b0696f8197b2ea7a660c90b
Timestamp: 1760955044 Timestamp [UCT]: 2025-10-20 10:10:44 Age [y:d:h:m:s]: 00:105:04:19:02
Block: 1393992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75118 RingCT/type: yes/0
Extra: 01d4cdc2f61ec5f042f920d3f7d3b78dad1fba064e2b0696f8197b2ea7a660c90b021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0822c11622a024125d9e1ca6a47ca2bc05a2ff840dc1bc1ced0e4186d40734df 0.600000000000 1882259 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": 1394002, "vin": [ { "gen": { "height": 1393992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0822c11622a024125d9e1ca6a47ca2bc05a2ff840dc1bc1ced0e4186d40734df" } } ], "extra": [ 1, 212, 205, 194, 246, 30, 197, 240, 66, 249, 32, 211, 247, 211, 183, 141, 173, 31, 186, 6, 78, 43, 6, 150, 248, 25, 123, 46, 167, 166, 96, 201, 11, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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