Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970ea63fa778d52505d94b61355b4e57f58d0cb512e50ba06df86b934a30407d

Tx prefix hash: f157267e5057601a2bdeed3ed75c58d5ef335421d5fd6c8e200d6c4319ce297c
Tx public key: 7e4c98e041ee2a6e453ce4b6d3a23821f3480ba5abaa721f1e77e3ec06fa7fd1
Timestamp: 1686115067 Timestamp [UCT]: 2023-06-07 05:17:47 Age [y:d:h:m:s]: 01:340:23:16:01
Block: 776877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504905 RingCT/type: yes/0
Extra: 017e4c98e041ee2a6e453ce4b6d3a23821f3480ba5abaa721f1e77e3ec06fa7fd10211000000014b8f5122000000000000000000

1 output(s) for total of 1.636380011000 dcy

stealth address amount amount idx
00: ff186e2192ae3a31fea940e60977bdf1c71447d4d0035525d099b7bcad5bc7fe 1.636380011000 1226444 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": 776887, "vin": [ { "gen": { "height": 776877 } } ], "vout": [ { "amount": 1636380011, "target": { "key": "ff186e2192ae3a31fea940e60977bdf1c71447d4d0035525d099b7bcad5bc7fe" } } ], "extra": [ 1, 126, 76, 152, 224, 65, 238, 42, 110, 69, 60, 228, 182, 211, 162, 56, 33, 243, 72, 11, 165, 171, 170, 114, 31, 30, 119, 227, 236, 6, 250, 127, 209, 2, 17, 0, 0, 0, 1, 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