Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf8d1787b561d7471a5d983f362339fc688d3d8d23a9b61907d012e5402dc35c

Tx prefix hash: e24b21743741a377620f7159a9cad382c20aeaa2dfd110d6c459ff5fc6db5169
Tx public key: 1036f99213540dc093c40734cdad00617e8531b0c2ec297a2bf4425c88f9c655
Timestamp: 1710827031 Timestamp [UCT]: 2024-03-19 05:43:51 Age [y:d:h:m:s]: 01:025:18:37:37
Block: 981527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279400 RingCT/type: yes/0
Extra: 011036f99213540dc093c40734cdad00617e8531b0c2ec297a2bf4425c88f9c655021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e30d2dbd0982e0639e50c4bb454b000f913ea7b83df2e681d330606b21f14546 0.600000000000 1441624 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": 981537, "vin": [ { "gen": { "height": 981527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e30d2dbd0982e0639e50c4bb454b000f913ea7b83df2e681d330606b21f14546" } } ], "extra": [ 1, 16, 54, 249, 146, 19, 84, 13, 192, 147, 196, 7, 52, 205, 173, 0, 97, 126, 133, 49, 176, 194, 236, 41, 122, 43, 244, 66, 92, 136, 249, 198, 85, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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