Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abaa67ebb00ebcbe198512f075d8a5a5dc0d823848b6a22e3dc3087bc195b114

Tx prefix hash: 0bb003fc3c315bdc9787a61454f6ef7d76baab22bce7b54afc73aa59dcb54d50
Tx public key: 1c375c555aa0ded9a25ba6e7384e8b7411a7974e5f2e043ee52ea952094dfa06
Timestamp: 1727290648 Timestamp [UCT]: 2024-09-25 18:57:28 Age [y:d:h:m:s]: 00:149:18:22:58
Block: 1117999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106812 RingCT/type: yes/0
Extra: 011c375c555aa0ded9a25ba6e7384e8b7411a7974e5f2e043ee52ea952094dfa06021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b01fa286b7842890ab341ae9c081a435b1eab366e313092647bc5c1c37496e7f 0.600000000000 1599040 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": 1118009, "vin": [ { "gen": { "height": 1117999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b01fa286b7842890ab341ae9c081a435b1eab366e313092647bc5c1c37496e7f" } } ], "extra": [ 1, 28, 55, 92, 85, 90, 160, 222, 217, 162, 91, 166, 231, 56, 78, 139, 116, 17, 167, 151, 78, 95, 46, 4, 62, 229, 46, 169, 82, 9, 77, 250, 6, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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