Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8ac9bf39829dacb784390cfbebbe46ce5b5216148f5021084df0deb08a701c6

Tx prefix hash: c5dc47192d8813dc2e70d613c57ad515b4e182c7c56374c4d941ee58de94ccb0
Tx public key: cf728fe3f75fbe6c70da8fa3ed1bc0dfd736c0537286c9e13517cf17a362cdee
Timestamp: 1707233082 Timestamp [UCT]: 2024-02-06 15:24:42 Age [y:d:h:m:s]: 01:021:21:51:26
Block: 951700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276694 RingCT/type: yes/0
Extra: 01cf728fe3f75fbe6c70da8fa3ed1bc0dfd736c0537286c9e13517cf17a362cdee0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8ae8e4e4d39e28bcc40ca246b2ccdd50731863557d4af91052d913b835c0059 0.600000000000 1410504 of 15

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": 951710, "vin": [ { "gen": { "height": 951700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8ae8e4e4d39e28bcc40ca246b2ccdd50731863557d4af91052d913b835c0059" } } ], "extra": [ 1, 207, 114, 143, 227, 247, 95, 190, 108, 112, 218, 143, 163, 237, 27, 192, 223, 215, 54, 192, 83, 114, 134, 201, 225, 53, 23, 207, 23, 163, 98, 205, 238, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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