Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 203ca51118beac3e179b6d053991669e8389195ebe53d8df62c82151c363055f

Tx prefix hash: 49db586a019ba151c646f0480629268d041e3f50619804a12c3e9cc6ed86cb5b
Tx public key: f8a7c724e6bc4cc8a8b42fa765781e204f4578a79e0c6e82bdbc70df2d9e3ca8
Timestamp: 1583751525 Timestamp [UCT]: 2020-03-09 10:58:45 Age [y:d:h:m:s]: 05:100:08:11:32
Block: 79156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227271 RingCT/type: yes/0
Extra: 01f8a7c724e6bc4cc8a8b42fa765781e204f4578a79e0c6e82bdbc70df2d9e3ca80211000000013b1b9791000000000000000000

1 output(s) for total of 335.524396566000 dcy

stealth address amount amount idx
00: fc9f59526f63d9fc61ac1490e3300e6f1a4c3b1ecf8ee0e1afb7dc7ccb77e240 335.524396566000 144918 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": 79166, "vin": [ { "gen": { "height": 79156 } } ], "vout": [ { "amount": 335524396566, "target": { "key": "fc9f59526f63d9fc61ac1490e3300e6f1a4c3b1ecf8ee0e1afb7dc7ccb77e240" } } ], "extra": [ 1, 248, 167, 199, 36, 230, 188, 76, 200, 168, 180, 47, 167, 101, 120, 30, 32, 79, 69, 120, 167, 158, 12, 110, 130, 189, 188, 112, 223, 45, 158, 60, 168, 2, 17, 0, 0, 0, 1, 59, 27, 151, 145, 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