Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c89b2f3a0af50f11203b771d4d47228ffaf9e889456726f31d6e17daf7da56f

Tx prefix hash: 31047e416ff10e0feb546e011ec441f0ae6088fd09d4fbf85046105c1fd1d4f5
Tx public key: 65b0fd31b919a6d2d2e6ecc72e5719edcfe1634eef45ab4e66f3141efbbfe5a8
Timestamp: 1687983393 Timestamp [UCT]: 2023-06-28 20:16:33 Age [y:d:h:m:s]: 01:285:01:10:36
Block: 792375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464867 RingCT/type: yes/0
Extra: 0165b0fd31b919a6d2d2e6ecc72e5719edcfe1634eef45ab4e66f3141efbbfe5a80211000000014b8f5122000000000000000000

1 output(s) for total of 1.453894306000 dcy

stealth address amount amount idx
00: f08b820cc904e8bea4f405d424cab96d02ccc6b502b0d445d0bd286b91a46416 1.453894306000 1242972 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": 792385, "vin": [ { "gen": { "height": 792375 } } ], "vout": [ { "amount": 1453894306, "target": { "key": "f08b820cc904e8bea4f405d424cab96d02ccc6b502b0d445d0bd286b91a46416" } } ], "extra": [ 1, 101, 176, 253, 49, 185, 25, 166, 210, 210, 230, 236, 199, 46, 87, 25, 237, 207, 225, 99, 78, 239, 69, 171, 78, 102, 243, 20, 30, 251, 191, 229, 168, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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