Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25df2595cbbdfad4b03cfb05a764510fcd914b6881f4a96dcdee058a8b428cf1

Tx prefix hash: 616901a27053b229aebfccf53a71ca344723833b9f72644d417af3bd877d806a
Tx public key: 3e64a4ed5ba2d6f1cf768b998e1992531dd1ba4cb5ccd9066e792c5cd383a5b5
Timestamp: 1722529382 Timestamp [UCT]: 2024-08-01 16:23:02 Age [y:d:h:m:s]: 00:205:18:57:52
Block: 1078524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146937 RingCT/type: yes/0
Extra: 013e64a4ed5ba2d6f1cf768b998e1992531dd1ba4cb5ccd9066e792c5cd383a5b5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65c16d39f981e710e227719427836ecb5f2c5139ccf2eb7a897b8f62fcf24b2a 0.600000000000 1551103 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": 1078534, "vin": [ { "gen": { "height": 1078524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65c16d39f981e710e227719427836ecb5f2c5139ccf2eb7a897b8f62fcf24b2a" } } ], "extra": [ 1, 62, 100, 164, 237, 91, 162, 214, 241, 207, 118, 139, 153, 142, 25, 146, 83, 29, 209, 186, 76, 181, 204, 217, 6, 110, 121, 44, 92, 211, 131, 165, 181, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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