Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99f2cce9487838f0d32c326449eab372184146923c031dc49022c794ee0ddac3

Tx prefix hash: 522f0697fe3e44ff92c6ed889e8a329185df7c3cb8d7b53f80b2bf219800aab0
Tx public key: 8d10961ae1cb483a815e520fe82e51602e4c1cc6463531fc40cb131cce65ba7b
Timestamp: 1583457067 Timestamp [UCT]: 2020-03-06 01:11:07 Age [y:d:h:m:s]: 04:269:17:29:29
Block: 77188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087270 RingCT/type: yes/0
Extra: 018d10961ae1cb483a815e520fe82e51602e4c1cc6463531fc40cb131cce65ba7b02110000001fd81c26c0000000000000000000

1 output(s) for total of 340.600207184000 dcy

stealth address amount amount idx
00: 106b1c22e25751186702582fb0cb5b61eff5e7de83295960afb814c1c15435a0 340.600207184000 142068 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": 77198, "vin": [ { "gen": { "height": 77188 } } ], "vout": [ { "amount": 340600207184, "target": { "key": "106b1c22e25751186702582fb0cb5b61eff5e7de83295960afb814c1c15435a0" } } ], "extra": [ 1, 141, 16, 150, 26, 225, 203, 72, 58, 129, 94, 82, 15, 232, 46, 81, 96, 46, 76, 28, 198, 70, 53, 49, 252, 64, 203, 19, 28, 206, 101, 186, 123, 2, 17, 0, 0, 0, 31, 216, 28, 38, 192, 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