Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2ad36698ab28057333ebc2deca258939d311aea07a7de070ee341e83e3abd9

Tx prefix hash: 9e70e70b5f50300dc17b86327aec35cb2f99055ee7773816ed46b7027e76f74a
Tx public key: f36da8bdaa1b0bd3f4b7725ff60e41b3eabf7f5ee97e508d2da339c24b3b30ab
Timestamp: 1705872498 Timestamp [UCT]: 2024-01-21 21:28:18 Age [y:d:h:m:s]: 01:292:21:44:07
Block: 940397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468169 RingCT/type: yes/0
Extra: 01f36da8bdaa1b0bd3f4b7725ff60e41b3eabf7f5ee97e508d2da339c24b3b30ab02110000002352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bfc729600530d8275b510f8a7196e7455928cd188112cbd17ebcf5733679561 0.600000000000 1398533 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": 940407, "vin": [ { "gen": { "height": 940397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bfc729600530d8275b510f8a7196e7455928cd188112cbd17ebcf5733679561" } } ], "extra": [ 1, 243, 109, 168, 189, 170, 27, 11, 211, 244, 183, 114, 95, 246, 14, 65, 179, 234, 191, 127, 94, 233, 126, 80, 141, 45, 163, 57, 194, 75, 59, 48, 171, 2, 17, 0, 0, 0, 35, 82, 212, 126, 148, 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