Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d6311808dfd7c39e2cad5eebee2f92691629659f743fb8ce3ea73a4b8e3cfd9

Tx prefix hash: 756767ab65f6507434108b160ac53efbe2f6c364626d4bf7dfe474c9a4bb0b5a
Tx public key: 3e6aa71d7b173f4d22a8f3e4e35abad7af6f96a423ef55911a7180113ccd9caa
Timestamp: 1576427241 Timestamp [UCT]: 2019-12-15 16:27:21 Age [y:d:h:m:s]: 05:115:18:45:41
Block: 27773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1229165 RingCT/type: yes/0
Extra: 013e6aa71d7b173f4d22a8f3e4e35abad7af6f96a423ef55911a7180113ccd9caa0211000000359159db1e000000000000000000

1 output(s) for total of 496.566465866000 dcy

stealth address amount amount idx
00: 4b14d3157dc9594735cc6ba270d8d6645d79e1ed4129abd7cbdb32ecd18e6b76 496.566465866000 45827 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": 27783, "vin": [ { "gen": { "height": 27773 } } ], "vout": [ { "amount": 496566465866, "target": { "key": "4b14d3157dc9594735cc6ba270d8d6645d79e1ed4129abd7cbdb32ecd18e6b76" } } ], "extra": [ 1, 62, 106, 167, 29, 123, 23, 63, 77, 34, 168, 243, 228, 227, 90, 186, 215, 175, 111, 150, 164, 35, 239, 85, 145, 26, 113, 128, 17, 60, 205, 156, 170, 2, 17, 0, 0, 0, 53, 145, 89, 219, 30, 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