Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 435ad240c3cb09e9e59a2ccef5e37b30f4db380c76970f4360aab42bd57c67bb

Tx prefix hash: 94c7e78da813f6e5a13edbcf25cf7e17c375ec582e9a49cd6b9f4d2d9233b587
Tx public key: 56ea94cb775f903e143506d02ee79563fb01f23477b1ceac75a5000c6e61d304
Timestamp: 1729354995 Timestamp [UCT]: 2024-10-19 16:23:15 Age [y:d:h:m:s]: 00:175:15:43:58
Block: 1135108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125327 RingCT/type: yes/0
Extra: 0156ea94cb775f903e143506d02ee79563fb01f23477b1ceac75a5000c6e61d304021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d3e9d9d71132d8df06009cb205211aa6e3745078be6b1bf3fb3ff5f7f3b80fe 0.600000000000 1618437 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": 1135118, "vin": [ { "gen": { "height": 1135108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d3e9d9d71132d8df06009cb205211aa6e3745078be6b1bf3fb3ff5f7f3b80fe" } } ], "extra": [ 1, 86, 234, 148, 203, 119, 95, 144, 62, 20, 53, 6, 208, 46, 231, 149, 99, 251, 1, 242, 52, 119, 177, 206, 172, 117, 165, 0, 12, 110, 97, 211, 4, 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