Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eec7e9a65e26e6181abbbc3e3078a8468c6447cbc92725e45d04ce7ac0c3327b

Tx prefix hash: 52719de0867e8e8f46c7f5ba1f22d7afc9ce56c1dce6f830ac8a05830701209f
Tx public key: 269b7f3220816f5af8aa132ee319886d142038ce0b361f7632dc97d380a96097
Timestamp: 1709176450 Timestamp [UCT]: 2024-02-29 03:14:10 Age [y:d:h:m:s]: 01:037:18:30:50
Block: 967828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287987 RingCT/type: yes/0
Extra: 01269b7f3220816f5af8aa132ee319886d142038ce0b361f7632dc97d380a9609702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a2a753c16fedc084db412c2944713754efba49febc657b4a7cfee715a8931a5 0.600000000000 1427619 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": 967838, "vin": [ { "gen": { "height": 967828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a2a753c16fedc084db412c2944713754efba49febc657b4a7cfee715a8931a5" } } ], "extra": [ 1, 38, 155, 127, 50, 32, 129, 111, 90, 248, 170, 19, 46, 227, 25, 136, 109, 20, 32, 56, 206, 11, 54, 31, 118, 50, 220, 151, 211, 128, 169, 96, 151, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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