Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74a9f9c691480300fc90ffa2664dae5b9b8a8f25473bd12c6c225d835353ee11

Tx prefix hash: 9d3c60d442dfc7fcc7b9cd94346033f0d689661ae779a8ec583fb23d8704205e
Tx public key: 8347187ed938e79d02baa2cefaa2d3ae7f080047d538c49fda7365e9d88b30b6
Timestamp: 1696128566 Timestamp [UCT]: 2023-10-01 02:49:26 Age [y:d:h:m:s]: 01:236:07:13:38
Block: 859850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429976 RingCT/type: yes/0
Extra: 018347187ed938e79d02baa2cefaa2d3ae7f080047d538c49fda7365e9d88b30b602110000000333af99f4000000000000000000

1 output(s) for total of 0.868880502000 dcy

stealth address amount amount idx
00: 14829954e04e17e882040d3ee94446ed02f440eb0e49c34cabfda18c9d1b3a64 0.868880502000 1314100 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": 859860, "vin": [ { "gen": { "height": 859850 } } ], "vout": [ { "amount": 868880502, "target": { "key": "14829954e04e17e882040d3ee94446ed02f440eb0e49c34cabfda18c9d1b3a64" } } ], "extra": [ 1, 131, 71, 24, 126, 217, 56, 231, 157, 2, 186, 162, 206, 250, 162, 211, 174, 127, 8, 0, 71, 213, 56, 196, 159, 218, 115, 101, 233, 216, 139, 48, 182, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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