Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7a1ee8d2b9f0946438dd1e792239419fd9253fc84a9fe426240063a0ca3c54a

Tx prefix hash: 0e7740ee28107e60bfe4251bfc695ca97eb9d2c30a59418795b2822c9d7e2bc8
Tx public key: a2e903560cc93c9862e75063b8aa42b75af03717954612082332ac4f99c3c7c1
Timestamp: 1625623688 Timestamp [UCT]: 2021-07-07 02:08:08 Age [y:d:h:m:s]: 04:094:18:42:01
Block: 289395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1096293 RingCT/type: yes/0
Extra: 01a2e903560cc93c9862e75063b8aa42b75af03717954612082332ac4f99c3c7c102110000000c694a138f000000000000000000

1 output(s) for total of 67.470625665000 dcy

stealth address amount amount idx
00: 874f1a99fd8891789d39a9f195502204afabdaa200f662e88b9b71d82b7cb5f5 67.470625665000 606103 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": 289405, "vin": [ { "gen": { "height": 289395 } } ], "vout": [ { "amount": 67470625665, "target": { "key": "874f1a99fd8891789d39a9f195502204afabdaa200f662e88b9b71d82b7cb5f5" } } ], "extra": [ 1, 162, 233, 3, 86, 12, 201, 60, 152, 98, 231, 80, 99, 184, 170, 66, 183, 90, 240, 55, 23, 149, 70, 18, 8, 35, 50, 172, 79, 153, 195, 199, 193, 2, 17, 0, 0, 0, 12, 105, 74, 19, 143, 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