Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b28b6342123383962927d23b3510be6a89d08a288e6e6c31bfd3e716b925b41c

Tx prefix hash: 8a802dc51423725e7cb6f93dbf66eab90c3328f547ac51f8411ad139aa9dffd0
Tx public key: 117b1cb6baae72ad07ae24e30bcd028d47ed9b21890133dd7e45b042a95f8c15
Timestamp: 1732304325 Timestamp [UCT]: 2024-11-22 19:38:45 Age [y:d:h:m:s]: 00:001:01:53:52
Block: 1159471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 764 RingCT/type: yes/0
Extra: 01117b1cb6baae72ad07ae24e30bcd028d47ed9b21890133dd7e45b042a95f8c15021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 291398ab2e20385a84782602889bddcce7fbc41a8cf17ff8f7cb0bd1a90477df 0.600000000000 1645108 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": 1159481, "vin": [ { "gen": { "height": 1159471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "291398ab2e20385a84782602889bddcce7fbc41a8cf17ff8f7cb0bd1a90477df" } } ], "extra": [ 1, 17, 123, 28, 182, 186, 174, 114, 173, 7, 174, 36, 227, 11, 205, 2, 141, 71, 237, 155, 33, 137, 1, 51, 221, 126, 69, 176, 66, 169, 95, 140, 21, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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