Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0160b4139c4fc1adb867384df4ca4645686c64f8390faf7e79f80832440ba0e5

Tx prefix hash: 9fd1fd1ccd3657d9b637ed5b24f1c66da7ed9da66a1fcac2753e870f0996dfb4
Tx public key: 21017df3ad35c66060b54e0df6f6a941c8409061e6cb68fdb828517300b782c5
Timestamp: 1714368334 Timestamp [UCT]: 2024-04-29 05:25:34 Age [y:d:h:m:s]: 00:256:07:49:30
Block: 1010864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183466 RingCT/type: yes/0
Extra: 0121017df3ad35c66060b54e0df6f6a941c8409061e6cb68fdb828517300b782c502110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae767f4d60f8b7fa6219567eddc48592f654c4db68d55b41ce926cc148e0046 0.600000000000 1472934 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": 1010874, "vin": [ { "gen": { "height": 1010864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae767f4d60f8b7fa6219567eddc48592f654c4db68d55b41ce926cc148e0046" } } ], "extra": [ 1, 33, 1, 125, 243, 173, 53, 198, 96, 96, 181, 78, 13, 246, 246, 169, 65, 200, 64, 144, 97, 230, 203, 104, 253, 184, 40, 81, 115, 0, 183, 130, 197, 2, 17, 0, 0, 0, 4, 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