Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4140328575c2c16be4a44a385a160038ffe58a7b2135f5b0e9ef7ed68968de94

Tx prefix hash: a4222d7ea0d9b929a2a2e814c0a870f95cc19117a929a2500fa0125296721a4a
Tx public key: ca513fd5c0f619eaf91dfcf74dc566de2ddd3d667c35fc2a9a239fdbac12d677
Timestamp: 1720420344 Timestamp [UCT]: 2024-07-08 06:32:24 Age [y:d:h:m:s]: 00:284:08:10:14
Block: 1061046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203165 RingCT/type: yes/0
Extra: 01ca513fd5c0f619eaf91dfcf74dc566de2ddd3d667c35fc2a9a239fdbac12d677021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a05fcf3c6c6ff8bb1aba3b355288c61b25da4ea6bec2870e3ad844e4592026de 0.600000000000 1531537 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": 1061056, "vin": [ { "gen": { "height": 1061046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a05fcf3c6c6ff8bb1aba3b355288c61b25da4ea6bec2870e3ad844e4592026de" } } ], "extra": [ 1, 202, 81, 63, 213, 192, 246, 25, 234, 249, 29, 252, 247, 77, 197, 102, 222, 45, 221, 61, 102, 124, 53, 252, 42, 154, 35, 159, 219, 172, 18, 214, 119, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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