Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48f1fe19b97c9f3b9f3cfc6f36fe7eaa7cd49d71aa160f75f235490d399531ca

Tx prefix hash: dca0bbd674f36cc73f626f8ab7493c6519f2934fb07d69995686cc5fc0db30d7
Tx public key: 7a6854bf3dce9e0164ad77f463d76bcf920888876d30a100d470b9c19acd9707
Timestamp: 1712462106 Timestamp [UCT]: 2024-04-07 03:55:06 Age [y:d:h:m:s]: 01:213:07:05:45
Block: 995033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411124 RingCT/type: yes/0
Extra: 017a6854bf3dce9e0164ad77f463d76bcf920888876d30a100d470b9c19acd97070211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d99685bc2c2c24cd05e42e9478c7b1e88c35cff1d2e9898d1fd74fbc12689c43 0.600000000000 1455437 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": 995043, "vin": [ { "gen": { "height": 995033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d99685bc2c2c24cd05e42e9478c7b1e88c35cff1d2e9898d1fd74fbc12689c43" } } ], "extra": [ 1, 122, 104, 84, 191, 61, 206, 158, 1, 100, 173, 119, 244, 99, 215, 107, 207, 146, 8, 136, 135, 109, 48, 161, 0, 212, 112, 185, 193, 154, 205, 151, 7, 2, 17, 0, 0, 0, 7, 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