Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3e7b0af61d223ee0cf0ff634b1112d2b66a1ee507d5c08e98e3be8b4aeef9f8

Tx prefix hash: cd3f9b8b94042761c971b16233016ccc06c48d1be58abf89cf6d3b52b5fbee8e
Tx public key: e446ef7f70fb71678eea38cd0306b70538c074f80b0cee6f3113b7908d0102f2
Timestamp: 1719243631 Timestamp [UCT]: 2024-06-24 15:40:31 Age [y:d:h:m:s]: 00:241:23:58:51
Block: 1051269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172877 RingCT/type: yes/0
Extra: 01e446ef7f70fb71678eea38cd0306b70538c074f80b0cee6f3113b7908d0102f20211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5396d099f6fbdf2fe4328de0120950fa213d6dd257295bac446d85ce6f0b081f 0.600000000000 1521578 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": 1051279, "vin": [ { "gen": { "height": 1051269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5396d099f6fbdf2fe4328de0120950fa213d6dd257295bac446d85ce6f0b081f" } } ], "extra": [ 1, 228, 70, 239, 127, 112, 251, 113, 103, 142, 234, 56, 205, 3, 6, 183, 5, 56, 192, 116, 248, 11, 12, 238, 111, 49, 19, 183, 144, 141, 1, 2, 242, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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