Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a021c30f2d2b1ed7a478b433a1316e8a7efc1b6738fca2d4a60e1d587ed65286

Tx prefix hash: d38c9298a8e587a3eb7f6d109c131d945c88078359839ab29d66b6afa4bbfbe0
Tx public key: fe09e75d428bf98a9313e453a3a581a5062e7825c7efe1c13d5c5e73d355c5fc
Timestamp: 1724405246 Timestamp [UCT]: 2024-08-23 09:27:26 Age [y:d:h:m:s]: 00:291:12:09:11
Block: 1094097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208230 RingCT/type: yes/0
Extra: 01fe09e75d428bf98a9313e453a3a581a5062e7825c7efe1c13d5c5e73d355c5fc021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b0c83bf5ba9749933289a143025bc7828f9b384fc81b5681972b533a48b7414 0.600000000000 1569170 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": 1094107, "vin": [ { "gen": { "height": 1094097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b0c83bf5ba9749933289a143025bc7828f9b384fc81b5681972b533a48b7414" } } ], "extra": [ 1, 254, 9, 231, 93, 66, 139, 249, 138, 147, 19, 228, 83, 163, 165, 129, 165, 6, 46, 120, 37, 199, 239, 225, 193, 61, 92, 94, 115, 211, 85, 197, 252, 2, 17, 0, 0, 0, 19, 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