Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d9ef37df05401cfdb028abbbd0047605306dbdde5bf5ea111e4823e7d7873dc

Tx prefix hash: 083b7f6803bb9f966543513b470438b793e24438cf800765d8e1d2ef33dee328
Tx public key: 679a22cdc5e7f1a4dbc5999f8b28e691d7c5cdf4b48a3fc1d4ade32b64d1cef7
Timestamp: 1659145067 Timestamp [UCT]: 2022-07-30 01:37:47 Age [y:d:h:m:s]: 02:238:07:28:26
Block: 554643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 691508 RingCT/type: yes/0
Extra: 01679a22cdc5e7f1a4dbc5999f8b28e691d7c5cdf4b48a3fc1d4ade32b64d1cef7021100000006e6d27f9c000000000000000000

1 output(s) for total of 8.917387174000 dcy

stealth address amount amount idx
00: 85498827944f29e3126314a50b47544191fc3b2c1487b39cf3e12411af54f215 8.917387174000 986499 of 0

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": 554653, "vin": [ { "gen": { "height": 554643 } } ], "vout": [ { "amount": 8917387174, "target": { "key": "85498827944f29e3126314a50b47544191fc3b2c1487b39cf3e12411af54f215" } } ], "extra": [ 1, 103, 154, 34, 205, 197, 231, 241, 164, 219, 197, 153, 159, 139, 40, 230, 145, 215, 197, 205, 244, 180, 138, 63, 193, 212, 173, 227, 43, 100, 209, 206, 247, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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