Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7eb03ea008ea2ed53dee174276a31db5f9c57c4670659bb0dcb4298fa795dd1

Tx prefix hash: 1e261bb80a5a00823f3f37471bd52d4537a776c71246af69bea5e0bd004aeaeb
Tx public key: efc17881a4e609d5755c18c50e9f549ec8c28e4ee69c421c42319302933cf726
Timestamp: 1580780984 Timestamp [UCT]: 2020-02-04 01:49:44 Age [y:d:h:m:s]: 05:007:23:14:36
Block: 57974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157902 RingCT/type: yes/0
Extra: 01efc17881a4e609d5755c18c50e9f549ec8c28e4ee69c421c42319302933cf7260211000000088a2ee0d9000000000000000000

1 output(s) for total of 394.374560996000 dcy

stealth address amount amount idx
00: 547952bef8c8877e242cb55def63ec9440db5fbe6351dbf115fd2dfa3f54b1bf 394.374560996000 107233 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": 57984, "vin": [ { "gen": { "height": 57974 } } ], "vout": [ { "amount": 394374560996, "target": { "key": "547952bef8c8877e242cb55def63ec9440db5fbe6351dbf115fd2dfa3f54b1bf" } } ], "extra": [ 1, 239, 193, 120, 129, 164, 230, 9, 213, 117, 92, 24, 197, 14, 159, 84, 158, 200, 194, 142, 78, 230, 156, 66, 28, 66, 49, 147, 2, 147, 60, 247, 38, 2, 17, 0, 0, 0, 8, 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