Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705cdc65a4193ad0fef38ebdc48f6d3486ca77e1f39a904bc76be16ac87696fa

Tx prefix hash: 46370f1275300438a127b3203d307804eeeb7e126a8ec32f64b9e350ec865655
Tx public key: f35fb8f70fea4c4ea6e63f239cf93e97dafe4299ab9c6c431db6a605c2422e5e
Timestamp: 1638696957 Timestamp [UCT]: 2021-12-05 09:35:57 Age [y:d:h:m:s]: 03:065:16:33:57
Block: 388858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 825622 RingCT/type: yes/0
Extra: 01f35fb8f70fea4c4ea6e63f239cf93e97dafe4299ab9c6c431db6a605c2422e5e021100000001a272b9cb000000000000000000

1 output(s) for total of 31.590201138000 dcy

stealth address amount amount idx
00: 52ed0520637a9992c0ea2e3a94c23ef28b4913f97054927b4955e5d339a1d60f 31.590201138000 783737 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": 388868, "vin": [ { "gen": { "height": 388858 } } ], "vout": [ { "amount": 31590201138, "target": { "key": "52ed0520637a9992c0ea2e3a94c23ef28b4913f97054927b4955e5d339a1d60f" } } ], "extra": [ 1, 243, 95, 184, 247, 15, 234, 76, 78, 166, 230, 63, 35, 156, 249, 62, 151, 218, 254, 66, 153, 171, 156, 108, 67, 29, 182, 166, 5, 194, 66, 46, 94, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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