Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09f785af7cbe1c4312e74eb236c2fdf4506b5731c5e767863b3e0e91bfec5185

Tx prefix hash: 46c453072bdcb62df08ca26ba73e476b5daa7a6de16496bff4c49434c7db68b5
Tx public key: 0e1002a7d593a60e5c364aa1683c48aaf262787f9915a6de90fd47a4c8e96a01
Timestamp: 1700298764 Timestamp [UCT]: 2023-11-18 09:12:44 Age [y:d:h:m:s]: 01:104:03:01:45
Block: 894217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335571 RingCT/type: yes/0
Extra: 010e1002a7d593a60e5c364aa1683c48aaf262787f9915a6de90fd47a4c8e96a010211000000024b8f5122000000000000000000

1 output(s) for total of 0.668479146000 dcy

stealth address amount amount idx
00: 89afcbc06e31d13a976c7cdf199ab350fbda763ed79d6d096f83f455afb3f114 0.668479146000 1350410 of 0

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": 894227, "vin": [ { "gen": { "height": 894217 } } ], "vout": [ { "amount": 668479146, "target": { "key": "89afcbc06e31d13a976c7cdf199ab350fbda763ed79d6d096f83f455afb3f114" } } ], "extra": [ 1, 14, 16, 2, 167, 213, 147, 166, 14, 92, 54, 74, 161, 104, 60, 72, 170, 242, 98, 120, 127, 153, 21, 166, 222, 144, 253, 71, 164, 200, 233, 106, 1, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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