Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 312af9d057d6c875faedd4d3ed2ca209ca6f8f30254553a1ee8b6dc0f0382598

Tx prefix hash: 145e9348fb52f93a441e283c6d5a8ae26859fe301d64a7ffbd64f18053c4d45e
Tx public key: caaa648a475cdbf8441437a31bdf395796396e013ee7aece9fbc8a1fed2d91ba
Timestamp: 1733151577 Timestamp [UCT]: 2024-12-02 14:59:37 Age [y:d:h:m:s]: 00:025:20:08:17
Block: 1166491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18481 RingCT/type: yes/0
Extra: 01caaa648a475cdbf8441437a31bdf395796396e013ee7aece9fbc8a1fed2d91ba021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd78b9bf0652f08013a8b81a66fa6a78d3f05decd39b0a2b5d87f543b31d3da8 0.600000000000 1652178 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": 1166501, "vin": [ { "gen": { "height": 1166491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd78b9bf0652f08013a8b81a66fa6a78d3f05decd39b0a2b5d87f543b31d3da8" } } ], "extra": [ 1, 202, 170, 100, 138, 71, 92, 219, 248, 68, 20, 55, 163, 27, 223, 57, 87, 150, 57, 110, 1, 62, 231, 174, 206, 159, 188, 138, 31, 237, 45, 145, 186, 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