Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efbcbf82f08b3e51f8332c6862ac78ae04ed4a9dcdc9edd2c25613ae44dbfc4c

Tx prefix hash: 771c41eb2cf02271649d4812eacb618992e75dfbd9de48bf32383ec7ebff2a42
Tx public key: 23566d9af4cab466dc78eb03a51d691ccf78cf0a1d53c11b0085f0c7fc95268d
Timestamp: 1577697038 Timestamp [UCT]: 2019-12-30 09:10:38 Age [y:d:h:m:s]: 05:041:09:09:33
Block: 34899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179355 RingCT/type: yes/0
Extra: 0123566d9af4cab466dc78eb03a51d691ccf78cf0a1d53c11b0085f0c7fc95268d0211000000028a2ee0d9000000000000000000

1 output(s) for total of 470.290256220000 dcy

stealth address amount amount idx
00: 076bb68a3f92bb320545bca04308ac446e55c604ddff5d701fd120102d8dff59 470.290256220000 58802 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": 34909, "vin": [ { "gen": { "height": 34899 } } ], "vout": [ { "amount": 470290256220, "target": { "key": "076bb68a3f92bb320545bca04308ac446e55c604ddff5d701fd120102d8dff59" } } ], "extra": [ 1, 35, 86, 109, 154, 244, 202, 180, 102, 220, 120, 235, 3, 165, 29, 105, 28, 207, 120, 207, 10, 29, 83, 193, 27, 0, 133, 240, 199, 252, 149, 38, 141, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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