Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d603a750dcbecfcf9f4a5c1375ec2316372b80379b72186afc583b81685a7009

Tx prefix hash: 933672ec756d1c1f8c34930cfd8970c8e9444253a457f77382018bae0f66c28a
Tx public key: a32795f8c799cf16641f2c53cf5071d51f96e4fd6f5dfa01fb553e1d58880b1a
Timestamp: 1714710131 Timestamp [UCT]: 2024-05-03 04:22:11 Age [y:d:h:m:s]: 01:027:22:55:33
Block: 1013705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280922 RingCT/type: yes/0
Extra: 01a32795f8c799cf16641f2c53cf5071d51f96e4fd6f5dfa01fb553e1d58880b1a0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c21cc0efcab8c6fa6748c46d66c1c2ed142a89ccc3d97773948330a33732a94 0.600000000000 1476592 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": 1013715, "vin": [ { "gen": { "height": 1013705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c21cc0efcab8c6fa6748c46d66c1c2ed142a89ccc3d97773948330a33732a94" } } ], "extra": [ 1, 163, 39, 149, 248, 199, 153, 207, 22, 100, 31, 44, 83, 207, 80, 113, 213, 31, 150, 228, 253, 111, 93, 250, 1, 251, 85, 62, 29, 88, 136, 11, 26, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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