Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e1a5d7b447370c505bc2a4a589d4e958cf3556c3dd73d9b68e7a4d39fb2327a

Tx prefix hash: 1a5c317b9507d9606e96716d6dee2dc6c15a2e1e4a43dce53dad3ac4318d68b8
Tx public key: 880ba9d9911d81a394284d3d75c113ff0e8ac77a5d419f9c3305b6d3f88dba32
Timestamp: 1724000580 Timestamp [UCT]: 2024-08-18 17:03:00 Age [y:d:h:m:s]: 00:188:00:02:32
Block: 1090727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134190 RingCT/type: yes/0
Extra: 01880ba9d9911d81a394284d3d75c113ff0e8ac77a5d419f9c3305b6d3f88dba3202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6c6ba8cbb21a74a449a1308c0b6730a126fd0e2142385f46714dc34ef5b1101 0.600000000000 1565350 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": 1090737, "vin": [ { "gen": { "height": 1090727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6c6ba8cbb21a74a449a1308c0b6730a126fd0e2142385f46714dc34ef5b1101" } } ], "extra": [ 1, 136, 11, 169, 217, 145, 29, 129, 163, 148, 40, 77, 61, 117, 193, 19, 255, 14, 138, 199, 122, 93, 65, 159, 156, 51, 5, 182, 211, 248, 141, 186, 50, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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