Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 038e323a69741d5527bb24583e981b55ff33d451c79414cf432214f89081e055

Tx prefix hash: eebcc62d8e6436be401defd2a2b87e5c436810ab650369e75da3016f6707f60f
Tx public key: 4d4adede63bc0fb9a88b6d1326af220e330e131d17ac79e2e0ad21ca0f56e33e
Timestamp: 1582243565 Timestamp [UCT]: 2020-02-21 00:06:05 Age [y:d:h:m:s]: 05:278:04:15:30
Block: 69007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1349851 RingCT/type: yes/0
Extra: 014d4adede63bc0fb9a88b6d1326af220e330e131d17ac79e2e0ad21ca0f56e33e0211000000158a2ee0d9000000000000000000

1 output(s) for total of 363.111142247000 dcy

stealth address amount amount idx
00: 165035c05d668dd75a70b8668095dfcef8f15c8c9e53ef1d053146c5212d5e4a 363.111142247000 127292 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": 69017, "vin": [ { "gen": { "height": 69007 } } ], "vout": [ { "amount": 363111142247, "target": { "key": "165035c05d668dd75a70b8668095dfcef8f15c8c9e53ef1d053146c5212d5e4a" } } ], "extra": [ 1, 77, 74, 222, 222, 99, 188, 15, 185, 168, 139, 109, 19, 38, 175, 34, 14, 51, 14, 19, 29, 23, 172, 121, 226, 224, 173, 33, 202, 15, 86, 227, 62, 2, 17, 0, 0, 0, 21, 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