Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bb328c0ce2dd11e369a3e78a56fc9bd17e5afd9b0e62491fe45572ebba2be98

Tx prefix hash: 0f6d07c8dc4b89353908d15fc00af503a780bb1f022d116581e80220620a2451
Tx public key: cc47efa2c3d35fc14b908e09ba3113dc80f1836fc7812319279836d5bfed88b6
Timestamp: 1707945810 Timestamp [UCT]: 2024-02-14 21:23:30 Age [y:d:h:m:s]: 01:327:09:43:42
Block: 957611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492834 RingCT/type: yes/0
Extra: 01cc47efa2c3d35fc14b908e09ba3113dc80f1836fc7812319279836d5bfed88b6021100000007c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32d5f341c3f78ac386b9b0fa47b46c5ac3f0cdbdf7b3e4e09f878861b07dec80 0.600000000000 1416931 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": 957621, "vin": [ { "gen": { "height": 957611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32d5f341c3f78ac386b9b0fa47b46c5ac3f0cdbdf7b3e4e09f878861b07dec80" } } ], "extra": [ 1, 204, 71, 239, 162, 195, 211, 95, 193, 75, 144, 142, 9, 186, 49, 19, 220, 128, 241, 131, 111, 199, 129, 35, 25, 39, 152, 54, 213, 191, 237, 136, 182, 2, 17, 0, 0, 0, 7, 197, 69, 41, 96, 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