Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9230aa1efe2288f6d17f60ce41824d853efa3431f545b96d2afd8e1c6861eb89

Tx prefix hash: 550e7d8a43c52a78adccc952df1f9e75d970885d1f0a9c8e5d9e38f308c13e5b
Tx public key: e2c0526c615fbe7f1ae97437facfd42a15654bcc72d07fea31618e7140cbdae9
Timestamp: 1576928464 Timestamp [UCT]: 2019-12-21 11:41:04 Age [y:d:h:m:s]: 05:120:20:58:58
Block: 29345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1235397 RingCT/type: yes/0
Extra: 01e2c0526c615fbe7f1ae97437facfd42a15654bcc72d07fea31618e7140cbdae902110000003d9159db1e000000000000000000

1 output(s) for total of 490.646490261000 dcy

stealth address amount amount idx
00: b1990e5fec173dedb72423b57e5c26e2cd392eee2f3354a5e109e8c413d4db3d 490.646490261000 48177 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": 29355, "vin": [ { "gen": { "height": 29345 } } ], "vout": [ { "amount": 490646490261, "target": { "key": "b1990e5fec173dedb72423b57e5c26e2cd392eee2f3354a5e109e8c413d4db3d" } } ], "extra": [ 1, 226, 192, 82, 108, 97, 95, 190, 127, 26, 233, 116, 55, 250, 207, 212, 42, 21, 101, 75, 204, 114, 208, 127, 234, 49, 97, 142, 113, 64, 203, 218, 233, 2, 17, 0, 0, 0, 61, 145, 89, 219, 30, 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