Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a51745b159b5d151cd18a3092bd3253017d97675bab01c987c3560556ed27d7

Tx prefix hash: 2c59474b0f3140a6c7eaea23bea839a51dec61f55fbf4b434a6daa82ce7aaa7a
Tx public key: 2b19ad5d715cb54e1925cc6f9f8e81eef7b104dd9b27ae9b7b003d4758e58f11
Timestamp: 1737848615 Timestamp [UCT]: 2025-01-25 23:43:35 Age [y:d:h:m:s]: 00:146:00:28:49
Block: 1205338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104054 RingCT/type: yes/0
Extra: 012b19ad5d715cb54e1925cc6f9f8e81eef7b104dd9b27ae9b7b003d4758e58f11021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48c756e8838479a4a2a098e94e468711dbe3877208c167a587f38ce9b69fadae 0.600000000000 1692035 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": 1205348, "vin": [ { "gen": { "height": 1205338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48c756e8838479a4a2a098e94e468711dbe3877208c167a587f38ce9b69fadae" } } ], "extra": [ 1, 43, 25, 173, 93, 113, 92, 181, 78, 25, 37, 204, 111, 159, 142, 129, 238, 247, 177, 4, 221, 155, 39, 174, 155, 123, 0, 61, 71, 88, 229, 143, 17, 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