Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a29535ac1e5751ef52a7da444207510b41f7f87ddb92c9a30b1d0e75e563b751

Tx prefix hash: ffa96162d4b5d8823a41d9848e824e6691599b4c1f976ce4e47d48bf16d08ad4
Tx public key: afc22c1bf917f35f67afb5edc38f2eaa38f679c39b7913f03e05ad94fe3b403a
Timestamp: 1718570722 Timestamp [UCT]: 2024-06-16 20:45:22 Age [y:d:h:m:s]: 00:221:13:11:00
Block: 1045720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158486 RingCT/type: yes/0
Extra: 01afc22c1bf917f35f67afb5edc38f2eaa38f679c39b7913f03e05ad94fe3b403a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95cf94f46e6b1eaf762b992da45a5d3c9d39ad0fdd0a5a04f1fcfe136d0406cb 0.600000000000 1515367 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": 1045730, "vin": [ { "gen": { "height": 1045720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95cf94f46e6b1eaf762b992da45a5d3c9d39ad0fdd0a5a04f1fcfe136d0406cb" } } ], "extra": [ 1, 175, 194, 44, 27, 249, 23, 243, 95, 103, 175, 181, 237, 195, 143, 46, 170, 56, 246, 121, 195, 155, 121, 19, 240, 62, 5, 173, 148, 254, 59, 64, 58, 2, 17, 0, 0, 0, 1, 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