Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4026217ab2475a6e168dfc65e3b0d01395f7f6eb8aedefea11881b42dac43728

Tx prefix hash: 3690083cedaf88dcd944699087a50795564e7fa65935b19c6981b6277600f862
Tx public key: 31ddf7fbc87a426d9188613efc7ef5b92539c7c5eafda54c05b856decd740f3f
Timestamp: 1578830197 Timestamp [UCT]: 2020-01-12 11:56:37 Age [y:d:h:m:s]: 05:297:13:17:55
Block: 43917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1360535 RingCT/type: yes/0
Extra: 0131ddf7fbc87a426d9188613efc7ef5b92539c7c5eafda54c05b856decd740f3f02110000003abd0f9f9f000000000000000000

1 output(s) for total of 439.031038644000 dcy

stealth address amount amount idx
00: eaa067c3e4a8f5176d27c2bdfb7778feae032e5c3e8334b52bda8fa2c76efd50 439.031038644000 79719 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": 43927, "vin": [ { "gen": { "height": 43917 } } ], "vout": [ { "amount": 439031038644, "target": { "key": "eaa067c3e4a8f5176d27c2bdfb7778feae032e5c3e8334b52bda8fa2c76efd50" } } ], "extra": [ 1, 49, 221, 247, 251, 200, 122, 66, 109, 145, 136, 97, 62, 252, 126, 245, 185, 37, 57, 199, 197, 234, 253, 165, 76, 5, 184, 86, 222, 205, 116, 15, 63, 2, 17, 0, 0, 0, 58, 189, 15, 159, 159, 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