Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b8fc7f9f5980547fa1790c933d284857a2cca198413137ed7fb8b35b6bcf873

Tx prefix hash: 3a52a111b9b051fe044905d0ea7311a206a55d341a6722e5433c639fdadb5e1e
Tx public key: 47be9d01d6359f0fe57bda019f50685246165b3cec448e9c68d87ed12db52101
Timestamp: 1705363534 Timestamp [UCT]: 2024-01-16 00:05:34 Age [y:d:h:m:s]: 01:129:03:39:05
Block: 936193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353457 RingCT/type: yes/0
Extra: 0147be9d01d6359f0fe57bda019f50685246165b3cec448e9c68d87ed12db5210102110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3b9b93d95dd7a32258c68b36ae3479ebf356d7b94e2254baf846108af1ae7e3 0.600000000000 1394217 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": 936203, "vin": [ { "gen": { "height": 936193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3b9b93d95dd7a32258c68b36ae3479ebf356d7b94e2254baf846108af1ae7e3" } } ], "extra": [ 1, 71, 190, 157, 1, 214, 53, 159, 15, 229, 123, 218, 1, 159, 80, 104, 82, 70, 22, 91, 60, 236, 68, 142, 156, 104, 216, 126, 209, 45, 181, 33, 1, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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