Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9524d2d5cbe820ba25f93b725e255f7f1a85847ac590b5390b0017d77171876

Tx prefix hash: dd7e6a1d6f261ffa06fe0dbf82c0062cd65bdc759fab433b3b8ae6c4ecc43a44
Tx public key: 687b798e0dc0c39543b226720ed197bad9cca16fb450dde1c6481e71e80686a3
Timestamp: 1710006506 Timestamp [UCT]: 2024-03-09 17:48:26 Age [y:d:h:m:s]: 01:076:21:24:43
Block: 974712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315987 RingCT/type: yes/0
Extra: 01687b798e0dc0c39543b226720ed197bad9cca16fb450dde1c6481e71e80686a302110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4657a2a4b1e60f100ea35d1b013066b3480e729f96f20a0c3acadbe8d3cc4073 0.600000000000 1434671 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": 974722, "vin": [ { "gen": { "height": 974712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4657a2a4b1e60f100ea35d1b013066b3480e729f96f20a0c3acadbe8d3cc4073" } } ], "extra": [ 1, 104, 123, 121, 142, 13, 192, 195, 149, 67, 178, 38, 114, 14, 209, 151, 186, 217, 204, 161, 111, 180, 80, 221, 225, 198, 72, 30, 113, 232, 6, 134, 163, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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