Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 900cbf264f19c4ce3216a78587c50401fed29ad6507a4c7129515456a2a3317b

Tx prefix hash: c744cdf9e2a1dcf6d89fd9fab763a0b93813293dcbc3c0585093b5ba12b18a63
Tx public key: c8f5ce84919c6b839e573669669b4fce9b528121f5ebf0b528d6d680f8c368c8
Timestamp: 1727032919 Timestamp [UCT]: 2024-09-22 19:21:59 Age [y:d:h:m:s]: 00:152:11:25:13
Block: 1115863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108745 RingCT/type: yes/0
Extra: 01c8f5ce84919c6b839e573669669b4fce9b528121f5ebf0b528d6d680f8c368c802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8cbc39cf64cde97146cc5381b23f96746d8b0e28b5cdfb6465799598988de89 0.600000000000 1596144 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": 1115873, "vin": [ { "gen": { "height": 1115863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8cbc39cf64cde97146cc5381b23f96746d8b0e28b5cdfb6465799598988de89" } } ], "extra": [ 1, 200, 245, 206, 132, 145, 156, 107, 131, 158, 87, 54, 105, 102, 155, 79, 206, 155, 82, 129, 33, 245, 235, 240, 181, 40, 214, 214, 128, 248, 195, 104, 200, 2, 17, 0, 0, 0, 4, 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