Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9e616971d692c370f88c5a6c06f8c525448318734d0acac1652621dc1b1b19f

Tx prefix hash: a99693ec75da7140854b67843650aa4d8568ae735aee32746df82ba3db2e0d1a
Tx public key: 831bb4536c5bb0206bdbc76a577c73fa6967460e75caf7e0c4d0f6a1b8549381
Timestamp: 1722486859 Timestamp [UCT]: 2024-08-01 04:34:19 Age [y:d:h:m:s]: 00:299:12:34:47
Block: 1078163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214017 RingCT/type: yes/0
Extra: 01831bb4536c5bb0206bdbc76a577c73fa6967460e75caf7e0c4d0f6a1b8549381021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be4f6c4aedb2b652669be695876d9e5ab0cd43b08e513d5f6108145cbfcbd60d 0.600000000000 1550730 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": 1078173, "vin": [ { "gen": { "height": 1078163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be4f6c4aedb2b652669be695876d9e5ab0cd43b08e513d5f6108145cbfcbd60d" } } ], "extra": [ 1, 131, 27, 180, 83, 108, 91, 176, 32, 107, 219, 199, 106, 87, 124, 115, 250, 105, 103, 70, 14, 117, 202, 247, 224, 196, 208, 246, 161, 184, 84, 147, 129, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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