Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9696c36e7aae206b1bd009a8a4c09feb68f3e66ef3039abe0bec4da3371aed18

Tx prefix hash: 983b7e0f532b4c438170c19af685a6b26902cdd643b8ad9bca9c973bad3c8a7e
Tx public key: 0fc8668760af27aed441f284d85f281c17724e56cd34ccd55f90a475a28c3fe0
Timestamp: 1706817935 Timestamp [UCT]: 2024-02-01 20:05:35 Age [y:d:h:m:s]: 00:350:00:41:45
Block: 948257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250584 RingCT/type: yes/0
Extra: 010fc8668760af27aed441f284d85f281c17724e56cd34ccd55f90a475a28c3fe002110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d48c7cf529b349c65af9f1df25272be87404bf9cc608a08fd235791e427121b2 0.600000000000 1406631 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": 948267, "vin": [ { "gen": { "height": 948257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d48c7cf529b349c65af9f1df25272be87404bf9cc608a08fd235791e427121b2" } } ], "extra": [ 1, 15, 200, 102, 135, 96, 175, 39, 174, 212, 65, 242, 132, 216, 95, 40, 28, 23, 114, 78, 86, 205, 52, 204, 213, 95, 144, 164, 117, 162, 140, 63, 224, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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