Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5c1985ac3c07de1e1b93ea21ee27178ca50a0ab6640b8723b1113d3110af13b

Tx prefix hash: 71f5857182743d0533502dddafde9b6c181d6e37d96825e2dd734baebed0a5d7
Tx public key: ca70af69e93530c6816eee278120ae0ab3f5fb5a06c7db06a7ed408874dfac08
Timestamp: 1734913530 Timestamp [UCT]: 2024-12-23 00:25:30 Age [y:d:h:m:s]: 00:101:19:58:37
Block: 1181112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72527 RingCT/type: yes/0
Extra: 01ca70af69e93530c6816eee278120ae0ab3f5fb5a06c7db06a7ed408874dfac080211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 999e14fadb93299f27ecda41cc6b7a1fe9ec7bc4f590d4e8129a965d1f6b60bf 0.600000000000 1667527 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": 1181122, "vin": [ { "gen": { "height": 1181112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "999e14fadb93299f27ecda41cc6b7a1fe9ec7bc4f590d4e8129a965d1f6b60bf" } } ], "extra": [ 1, 202, 112, 175, 105, 233, 53, 48, 198, 129, 110, 238, 39, 129, 32, 174, 10, 179, 245, 251, 90, 6, 199, 219, 6, 167, 237, 64, 136, 116, 223, 172, 8, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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