Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24ea11aed521b2b820c7c03f4bba1b0eb134831d264b9b0a727f85bc7ccc8743

Tx prefix hash: fc9c678df544892987e3cadff045716a71efb43e69d9355e63b89f5b43f6700d
Tx public key: 307ec2d7139fdf11e1d0282f5c478896e90a0a5143ed8a74901cb07ef4a8ac68
Timestamp: 1712136080 Timestamp [UCT]: 2024-04-03 09:21:20 Age [y:d:h:m:s]: 00:266:19:25:29
Block: 992326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191038 RingCT/type: yes/0
Extra: 01307ec2d7139fdf11e1d0282f5c478896e90a0a5143ed8a74901cb07ef4a8ac6802110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e64fe698b776c2b1df0f7246b1e4b75441c0f2c8c108a2d0ece1de67c230ea53 0.600000000000 1452666 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": 992336, "vin": [ { "gen": { "height": 992326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e64fe698b776c2b1df0f7246b1e4b75441c0f2c8c108a2d0ece1de67c230ea53" } } ], "extra": [ 1, 48, 126, 194, 215, 19, 159, 223, 17, 225, 208, 40, 47, 92, 71, 136, 150, 233, 10, 10, 81, 67, 237, 138, 116, 144, 28, 176, 126, 244, 168, 172, 104, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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