Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35676ea6ee9b3fe0ca923570e5980912041edc2b5fab0be7b637498404295c9f

Tx prefix hash: a6af1c57e0d21fd116dc422e701fcf061b713ea4503f1f5c3074a4611da24007
Tx public key: bf7ab9e42076796725a165abdb83b2e5cd8f904e9aef1bd5810511cf7fe63672
Timestamp: 1712673266 Timestamp [UCT]: 2024-04-09 14:34:26 Age [y:d:h:m:s]: 01:223:12:37:11
Block: 996788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418462 RingCT/type: yes/0
Extra: 01bf7ab9e42076796725a165abdb83b2e5cd8f904e9aef1bd5810511cf7fe63672021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6423b42ae72d81cafd43c7aa5f4cd03cf6e5d22c692367fe65b18e8eb2d4c5e8 0.600000000000 1457216 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": 996798, "vin": [ { "gen": { "height": 996788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6423b42ae72d81cafd43c7aa5f4cd03cf6e5d22c692367fe65b18e8eb2d4c5e8" } } ], "extra": [ 1, 191, 122, 185, 228, 32, 118, 121, 103, 37, 161, 101, 171, 219, 131, 178, 229, 205, 143, 144, 78, 154, 239, 27, 213, 129, 5, 17, 207, 127, 230, 54, 114, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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