Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25acaf7a3d32dd50c581942e2518a51c5a0a0c692b4158583b2c541063314c8e

Tx prefix hash: 89378c292ba1da0f1befa00f6f6fe89596524043abd65cfd01da401795b9a52d
Tx public key: 315a502bbffbd019b1a0e9c8de9d6feb95c4dc80f2a209ab31b6fb6f6733451b
Timestamp: 1574706679 Timestamp [UCT]: 2019-11-25 18:31:19 Age [y:d:h:m:s]: 05:005:08:10:56
Block: 17329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146642 RingCT/type: yes/0
Extra: 01315a502bbffbd019b1a0e9c8de9d6feb95c4dc80f2a209ab31b6fb6f6733451b021100000001f95225a5000000000000000000

1 output(s) for total of 537.764476849000 dcy

stealth address amount amount idx
00: 578ec31392f1468e8e2d591ec8aff57e2463a048faa566d7267b5bdd2a334ffc 537.764476849000 25045 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": 17339, "vin": [ { "gen": { "height": 17329 } } ], "vout": [ { "amount": 537764476849, "target": { "key": "578ec31392f1468e8e2d591ec8aff57e2463a048faa566d7267b5bdd2a334ffc" } } ], "extra": [ 1, 49, 90, 80, 43, 191, 251, 208, 25, 177, 160, 233, 200, 222, 157, 111, 235, 149, 196, 220, 128, 242, 162, 9, 171, 49, 182, 251, 111, 103, 51, 69, 27, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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