Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16030ad25be501f1b78299b9a7a567fd94545941fa86776a557c9e79c4b8ce74

Tx prefix hash: 54952481ab69e990ac45d766df4c9333778ffd92b94b663248c3454a48b6447a
Tx public key: 5d6b7001dde3c923feef2369c7cfaf9c9669e1d6f551ac8fd903be4ea99c2f48
Timestamp: 1719124168 Timestamp [UCT]: 2024-06-23 06:29:28 Age [y:d:h:m:s]: 00:122:04:46:57
Block: 1050279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87519 RingCT/type: yes/0
Extra: 015d6b7001dde3c923feef2369c7cfaf9c9669e1d6f551ac8fd903be4ea99c2f4802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4040bd3c3d1522e267643331de498d282e09eacb121da895d616d615268fb6a 0.600000000000 1520440 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": 1050289, "vin": [ { "gen": { "height": 1050279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4040bd3c3d1522e267643331de498d282e09eacb121da895d616d615268fb6a" } } ], "extra": [ 1, 93, 107, 112, 1, 221, 227, 201, 35, 254, 239, 35, 105, 199, 207, 175, 156, 150, 105, 225, 214, 245, 81, 172, 143, 217, 3, 190, 78, 169, 156, 47, 72, 2, 17, 0, 0, 0, 1, 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