Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 766e2e4ac95d11e211b62ad802eaeeddb77ea0169135aab0d7dccbdc80879a7f

Tx prefix hash: 73778cee962d133e1eaf54274288e59d87a47e18b6bd0a1cc665ae80862090f9
Tx public key: 1729f8c592d42db240647f049b5b90c1b6d5da8d2a6110964a6f356e3d75f99a
Timestamp: 1738647992 Timestamp [UCT]: 2025-02-04 05:46:32 Age [y:d:h:m:s]: 00:290:01:59:07
Block: 1211719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205081 RingCT/type: yes/0
Extra: 011729f8c592d42db240647f049b5b90c1b6d5da8d2a6110964a6f356e3d75f99a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e9997fa63109256b98ff1c4ca5d14089d0a89f8b4644ae4b26d9734eedf4149 0.600000000000 1698482 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": 1211729, "vin": [ { "gen": { "height": 1211719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e9997fa63109256b98ff1c4ca5d14089d0a89f8b4644ae4b26d9734eedf4149" } } ], "extra": [ 1, 23, 41, 248, 197, 146, 212, 45, 178, 64, 100, 127, 4, 155, 91, 144, 193, 182, 213, 218, 141, 42, 97, 16, 150, 74, 111, 53, 110, 61, 117, 249, 154, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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