Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aea2aecf238dbc25868d7da15aa0a55398ffd5f3ad63afa27b5f367e65182a4e

Tx prefix hash: dbb73355cafa66b29097f36a760d73b16c7208aa2dd2e2939a8edda82ab67301
Tx public key: 755fa100255131f5b277ca33d183df77a483a4f1d74f2ad19511006224b647d0
Timestamp: 1584914775 Timestamp [UCT]: 2020-03-22 22:06:15 Age [y:d:h:m:s]: 04:286:19:41:53
Block: 86693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102052 RingCT/type: yes/0
Extra: 01755fa100255131f5b277ca33d183df77a483a4f1d74f2ad19511006224b647d0021100000044c2c2f844000000000000000000

1 output(s) for total of 316.774988020000 dcy

stealth address amount amount idx
00: f56524e91af2d1d9e7c9d05c05fc3f8fd41599a1cc066ffc95a9c77562d83590 316.774988020000 156453 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": 86703, "vin": [ { "gen": { "height": 86693 } } ], "vout": [ { "amount": 316774988020, "target": { "key": "f56524e91af2d1d9e7c9d05c05fc3f8fd41599a1cc066ffc95a9c77562d83590" } } ], "extra": [ 1, 117, 95, 161, 0, 37, 81, 49, 245, 178, 119, 202, 51, 209, 131, 223, 119, 164, 131, 164, 241, 215, 79, 42, 209, 149, 17, 0, 98, 36, 182, 71, 208, 2, 17, 0, 0, 0, 68, 194, 194, 248, 68, 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