Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0027c50788ac5c90298a9cc64f22e0a76508ac8112168c615ff4bdde03406792

Tx prefix hash: 92b7aaf2490b8b6b88fad7d948d432d90e3b1257490615a1614c1ed0a82f45cd
Tx public key: 9a6ae8859298194e3160e5a8ae5b788eaa3519466ca9d64c9f491ff9434341b6
Timestamp: 1731265313 Timestamp [UCT]: 2024-11-10 19:01:53 Age [y:d:h:m:s]: 00:363:12:20:58
Block: 1150865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257344 RingCT/type: yes/0
Extra: 019a6ae8859298194e3160e5a8ae5b788eaa3519466ca9d64c9f491ff9434341b6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9faf94681d3bab9de6409702e1f127d47d26e34060b2a5ab4bffae625cd8b7c6 0.600000000000 1636286 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": 1150875, "vin": [ { "gen": { "height": 1150865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9faf94681d3bab9de6409702e1f127d47d26e34060b2a5ab4bffae625cd8b7c6" } } ], "extra": [ 1, 154, 106, 232, 133, 146, 152, 25, 78, 49, 96, 229, 168, 174, 91, 120, 142, 170, 53, 25, 70, 108, 169, 214, 76, 159, 73, 31, 249, 67, 67, 65, 182, 2, 17, 0, 0, 0, 2, 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