Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3b88d6d22dc448d92e3af66b5874e0d23a75deec8653e80961a462836a88271

Tx prefix hash: 4a7d29ab94cf7430805da819653716c918fb4f2b45403efd8f37ae098ed5f5b6
Tx public key: d941eef6700d34313455b7d68c32cbe963735a765ee10fd29e9685908d0af625
Timestamp: 1694512066 Timestamp [UCT]: 2023-09-12 09:47:46 Age [y:d:h:m:s]: 01:259:10:08:11
Block: 846430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446555 RingCT/type: yes/0
Extra: 01d941eef6700d34313455b7d68c32cbe963735a765ee10fd29e9685908d0af6250211000000064b8f5122000000000000000000

1 output(s) for total of 0.962556214000 dcy

stealth address amount amount idx
00: 549d2fe1826cf75802ff631b89adc78042dea945d3d252e99b6acda5eecad028 0.962556214000 1299890 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": 846440, "vin": [ { "gen": { "height": 846430 } } ], "vout": [ { "amount": 962556214, "target": { "key": "549d2fe1826cf75802ff631b89adc78042dea945d3d252e99b6acda5eecad028" } } ], "extra": [ 1, 217, 65, 238, 246, 112, 13, 52, 49, 52, 85, 183, 214, 140, 50, 203, 233, 99, 115, 90, 118, 94, 225, 15, 210, 158, 150, 133, 144, 141, 10, 246, 37, 2, 17, 0, 0, 0, 6, 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