Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c49c2362630ab31ab9ff76a025969e055f75ffaaa8351ab20450b34cc459e6a4

Tx prefix hash: fa9fd718821bf2c744223ff7c858f24c4e8cd52f909422c88ddbc98e97bc3770
Tx public key: 56c5e0f8bdb3f82754eb85cdab2aa5d1612da79079f224e709e1066cfd16a36e
Timestamp: 1711515126 Timestamp [UCT]: 2024-03-27 04:52:06 Age [y:d:h:m:s]: 01:067:17:07:16
Block: 987237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309383 RingCT/type: yes/0
Extra: 0156c5e0f8bdb3f82754eb85cdab2aa5d1612da79079f224e709e1066cfd16a36e0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdb7a790cc5cfcb9c7c9e6d9ca719c72056a2cec941c4975e719e603def24912 0.600000000000 1447478 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": 987247, "vin": [ { "gen": { "height": 987237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdb7a790cc5cfcb9c7c9e6d9ca719c72056a2cec941c4975e719e603def24912" } } ], "extra": [ 1, 86, 197, 224, 248, 189, 179, 248, 39, 84, 235, 133, 205, 171, 42, 165, 209, 97, 45, 167, 144, 121, 242, 36, 231, 9, 225, 6, 108, 253, 22, 163, 110, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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