Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441a35611e907d38a1cf9699605333b5b103aa419993a4052408d73a9b3ff98d

Tx prefix hash: 0f4560326207e4b4a4625818d22101a7a952fbbee67879d84622ef55ff593a15
Tx public key: 8d816df7741d0395a154b63e4bc86b1fbaa8210c25f0f27a9924217e8696120b
Timestamp: 1729641851 Timestamp [UCT]: 2024-10-23 00:04:11 Age [y:d:h:m:s]: 00:032:15:28:12
Block: 1137458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23331 RingCT/type: yes/0
Extra: 018d816df7741d0395a154b63e4bc86b1fbaa8210c25f0f27a9924217e8696120b02110000000192627dee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a63400893810472e6cb3bfb8d3cffad2a4bfb19a4c64a345abc4c676651d359d 0.600000000000 1620955 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": 1137468, "vin": [ { "gen": { "height": 1137458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a63400893810472e6cb3bfb8d3cffad2a4bfb19a4c64a345abc4c676651d359d" } } ], "extra": [ 1, 141, 129, 109, 247, 116, 29, 3, 149, 161, 84, 182, 62, 75, 200, 107, 31, 186, 168, 33, 12, 37, 240, 242, 122, 153, 36, 33, 126, 134, 150, 18, 11, 2, 17, 0, 0, 0, 1, 146, 98, 125, 238, 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