Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ae67e0aed442c085787173d0c6137f6a480f72f7366dd8e5c28fb1572446217

Tx prefix hash: c033a273cb0c514708395e472bee9cf2c7664feb4b1a1a1e845939c834ef1069
Tx public key: 2cefa08555c539b61adce3d1bb3bb2c634fb0e7a6520b0617f5eef2e95493fdc
Timestamp: 1689547016 Timestamp [UCT]: 2023-07-16 22:36:56 Age [y:d:h:m:s]: 01:187:12:38:23
Block: 805350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395323 RingCT/type: yes/0
Extra: 012cefa08555c539b61adce3d1bb3bb2c634fb0e7a6520b0617f5eef2e95493fdc02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.316865001000 dcy

stealth address amount amount idx
00: e9c9b16259da802cb680b5f61862f3131f007c647a1a295b78d44180e328e1e5 1.316865001000 1256575 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": 805360, "vin": [ { "gen": { "height": 805350 } } ], "vout": [ { "amount": 1316865001, "target": { "key": "e9c9b16259da802cb680b5f61862f3131f007c647a1a295b78d44180e328e1e5" } } ], "extra": [ 1, 44, 239, 160, 133, 85, 197, 57, 182, 26, 220, 227, 209, 187, 59, 178, 198, 52, 251, 14, 122, 101, 32, 176, 97, 127, 94, 239, 46, 149, 73, 63, 220, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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