Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e42658f2ad5cc2102d14e0ca5bc04d51dd5f05145d3538b204ab741638bbb9c

Tx prefix hash: 38721b825c3d66a2966e767fb3f51bc74f848a00f0184c5eee7e77d168402463
Tx public key: 2129b19d4187badd5c533f3f00c371f71a56ccecdb94d93a47eb4db3b4200c17
Timestamp: 1729622259 Timestamp [UCT]: 2024-10-22 18:37:39 Age [y:d:h:m:s]: 00:032:19:31:17
Block: 1137294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23444 RingCT/type: yes/0
Extra: 012129b19d4187badd5c533f3f00c371f71a56ccecdb94d93a47eb4db3b4200c17021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11af3b1bea95fb5fd240ac57dd9a32c466181202af095e27a28b7dfd8c34c8fd 0.600000000000 1620757 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": 1137304, "vin": [ { "gen": { "height": 1137294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11af3b1bea95fb5fd240ac57dd9a32c466181202af095e27a28b7dfd8c34c8fd" } } ], "extra": [ 1, 33, 41, 177, 157, 65, 135, 186, 221, 92, 83, 63, 63, 0, 195, 113, 247, 26, 86, 204, 236, 219, 148, 217, 58, 71, 235, 77, 179, 180, 32, 12, 23, 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