Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 292d57bdbcc50902ca7b238b15e555f2de01bafc09f4d630dd9dc1e8a0aa89ec

Tx prefix hash: 09180b8bfa5ab02bbe7255c82d265ef1f44275f7fa97bc2385e4b82b02cd9317
Tx public key: 48425f33b0d06731434fc2cf190ff5b2f8562b8db4c243fecf28dc0c080a5378
Timestamp: 1736432015 Timestamp [UCT]: 2025-01-09 14:13:35 Age [y:d:h:m:s]: 00:077:23:26:54
Block: 1193650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55503 RingCT/type: yes/0
Extra: 0148425f33b0d06731434fc2cf190ff5b2f8562b8db4c243fecf28dc0c080a53780211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e96489a4010ed5144ded05bba053e423213e15464c3647f9eec3c8cb0a7a0ed8 0.600000000000 1680213 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": 1193660, "vin": [ { "gen": { "height": 1193650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e96489a4010ed5144ded05bba053e423213e15464c3647f9eec3c8cb0a7a0ed8" } } ], "extra": [ 1, 72, 66, 95, 51, 176, 208, 103, 49, 67, 79, 194, 207, 25, 15, 245, 178, 248, 86, 43, 141, 180, 194, 67, 254, 207, 40, 220, 12, 8, 10, 83, 120, 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