Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1282100cc118c72c6561d824531271d13432404edca19f107d8ab2f811c8ae2b

Tx prefix hash: 6ff4cc60439b3cdc21cfa74812211e0467e06d18490c643a6caf295e35b4e3f1
Tx public key: c88223f5b6149ed66595f2bafb283b8c88391bd6b3fa825d1fc9a7cba0565a58
Timestamp: 1713733116 Timestamp [UCT]: 2024-04-21 20:58:36 Age [y:d:h:m:s]: 00:247:08:55:33
Block: 1005592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177084 RingCT/type: yes/0
Extra: 01c88223f5b6149ed66595f2bafb283b8c88391bd6b3fa825d1fc9a7cba0565a580211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b00239bb1a945525fc08769b1284e686c69b0ca71a566cd3a493a7f90e808f9 0.600000000000 1466334 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": 1005602, "vin": [ { "gen": { "height": 1005592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b00239bb1a945525fc08769b1284e686c69b0ca71a566cd3a493a7f90e808f9" } } ], "extra": [ 1, 200, 130, 35, 245, 182, 20, 158, 214, 101, 149, 242, 186, 251, 40, 59, 140, 136, 57, 27, 214, 179, 250, 130, 93, 31, 201, 167, 203, 160, 86, 90, 88, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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