Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4840bc6435b89135771c0a8c4d0e045f6005bd691e9824946bbd4643ee940ac

Tx prefix hash: ee481703b8df039edd460a76febc82fdd3548bf38f91ad30c917336ab7bf3fe3
Tx public key: 267a33d5193a39f00606578430c2df93336f1199ff8e388cf9da1f8e4d57169e
Timestamp: 1729520099 Timestamp [UCT]: 2024-10-21 14:14:59 Age [y:d:h:m:s]: 00:159:19:24:47
Block: 1136437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114029 RingCT/type: yes/0
Extra: 01267a33d5193a39f00606578430c2df93336f1199ff8e388cf9da1f8e4d57169e021100000002cab32bb9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c38665e065a1edc52c5b3c5ae175025d93a17feb9b3b6bd483561c0a3ef4979b 0.600000000000 1619782 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": 1136447, "vin": [ { "gen": { "height": 1136437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c38665e065a1edc52c5b3c5ae175025d93a17feb9b3b6bd483561c0a3ef4979b" } } ], "extra": [ 1, 38, 122, 51, 213, 25, 58, 57, 240, 6, 6, 87, 132, 48, 194, 223, 147, 51, 111, 17, 153, 255, 142, 56, 140, 249, 218, 31, 142, 77, 87, 22, 158, 2, 17, 0, 0, 0, 2, 202, 179, 43, 185, 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