Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 142e837f52f3bfc07c215f29fdd4004a7009ca805f8b3aa75a4a478f29c7459e

Tx prefix hash: f49fff82392e682d02bee64b11d3087f1d6183e6f7fdab00b6aa9e1b043b727d
Tx public key: 13fbe82e8d20c46e39ef292e8a99113df458aaef83265c03c9eacadff12c2fc3
Timestamp: 1577142595 Timestamp [UCT]: 2019-12-23 23:09:55 Age [y:d:h:m:s]: 05:080:19:18:33
Block: 30174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207688 RingCT/type: yes/0
Extra: 0113fbe82e8d20c46e39ef292e8a99113df458aaef83265c03c9eacadff12c2fc3021100000019d81c26c0000000000000000000

1 output(s) for total of 487.574856178000 dcy

stealth address amount amount idx
00: ece905dfe407030fe66afe8be514ca921a70c12d2d73ae52cd7915fae50670dd 487.574856178000 49822 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": 30184, "vin": [ { "gen": { "height": 30174 } } ], "vout": [ { "amount": 487574856178, "target": { "key": "ece905dfe407030fe66afe8be514ca921a70c12d2d73ae52cd7915fae50670dd" } } ], "extra": [ 1, 19, 251, 232, 46, 141, 32, 196, 110, 57, 239, 41, 46, 138, 153, 17, 61, 244, 88, 170, 239, 131, 38, 92, 3, 201, 234, 202, 223, 241, 44, 47, 195, 2, 17, 0, 0, 0, 25, 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