Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: def93028aba6143c70323622be7524690811a3b203c9f27fc32a5370378fd9a3

Tx prefix hash: 28ff6a7729bff24984341d27da5639ca33ef3854d5fe1d19d8e71148f067c0ff
Tx public key: 4698b794a9ffbaf89d5e9eb2e5ddefbdf0a218e61901b9a1e45cb3035ce25d06
Timestamp: 1716244646 Timestamp [UCT]: 2024-05-20 22:37:26 Age [y:d:h:m:s]: 00:156:23:52:48
Block: 1026422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112420 RingCT/type: yes/0
Extra: 014698b794a9ffbaf89d5e9eb2e5ddefbdf0a218e61901b9a1e45cb3035ce25d060211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8eec4775de585dd6ad32d6b56e2afe48453414765744ec7d9a79df4eba908cf 0.600000000000 1493501 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": 1026432, "vin": [ { "gen": { "height": 1026422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8eec4775de585dd6ad32d6b56e2afe48453414765744ec7d9a79df4eba908cf" } } ], "extra": [ 1, 70, 152, 183, 148, 169, 255, 186, 248, 157, 94, 158, 178, 229, 221, 239, 189, 240, 162, 24, 230, 25, 1, 185, 161, 228, 92, 179, 3, 92, 226, 93, 6, 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