Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7964c17fcc88b11941c282c784db1dbfd4d582a5584120c761d578217f9d28a

Tx prefix hash: 4a0a4028b488abac082ca89912c5ce22bf11cd28eaf8bc7fadfa7b4f87c7fdb6
Tx public key: 333e3d36eaeaf03a99f8de9b8ef9331627cf60fab939639b7d07e7d0869f7f99
Timestamp: 1628707943 Timestamp [UCT]: 2021-08-11 18:52:23 Age [y:d:h:m:s]: 03:108:11:46:41
Block: 311950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 850711 RingCT/type: yes/0
Extra: 01333e3d36eaeaf03a99f8de9b8ef9331627cf60fab939639b7d07e7d0869f7f9902110000000be6f80b5a000000000000000000

1 output(s) for total of 56.804223351000 dcy

stealth address amount amount idx
00: a43b70f58194f7dc677988df74c6d11a68b6fc1f9cdb39798e832de417e1b768 56.804223351000 649135 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": 311960, "vin": [ { "gen": { "height": 311950 } } ], "vout": [ { "amount": 56804223351, "target": { "key": "a43b70f58194f7dc677988df74c6d11a68b6fc1f9cdb39798e832de417e1b768" } } ], "extra": [ 1, 51, 62, 61, 54, 234, 234, 240, 58, 153, 248, 222, 155, 142, 249, 51, 22, 39, 207, 96, 250, 185, 57, 99, 155, 125, 7, 231, 208, 134, 159, 127, 153, 2, 17, 0, 0, 0, 11, 230, 248, 11, 90, 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