Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24e7185e61741ce1e1e7549cd67b211c509d23b4aa6d2f4fa29261238bb6f24c

Tx prefix hash: 64e02459ab8ec61aafe98f6c463eb9ea42d81938e01b56f6ac8110270a697d61
Tx public key: a49bdb224dfc517f1f312ad0dd580e9a612ccfa712cc27678e7ed5676e206f75
Timestamp: 1712900992 Timestamp [UCT]: 2024-04-12 05:49:52 Age [y:d:h:m:s]: 00:339:05:23:51
Block: 998676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242558 RingCT/type: yes/0
Extra: 01a49bdb224dfc517f1f312ad0dd580e9a612ccfa712cc27678e7ed5676e206f750211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5763ddb64e059a22348760701c5d795414b497c5ecd6883abf39e1cc7b2c3887 0.600000000000 1459128 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": 998686, "vin": [ { "gen": { "height": 998676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5763ddb64e059a22348760701c5d795414b497c5ecd6883abf39e1cc7b2c3887" } } ], "extra": [ 1, 164, 155, 219, 34, 77, 252, 81, 127, 31, 49, 42, 208, 221, 88, 14, 154, 97, 44, 207, 167, 18, 204, 39, 103, 142, 126, 213, 103, 110, 32, 111, 117, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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