Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d06ce913e0baa0f20d782812a0a631415f03bf1acbfb077fee4ac7d009701f6

Tx prefix hash: 67600219c1a5ad1755a7e92d6960f14a0847b5be9d21b5869838117b64007f4a
Tx public key: e8ec3100a908cdf183e3fa2dbf890fa9f5e11a79283ba9b36ba8d6db5d9f4055
Timestamp: 1725800706 Timestamp [UCT]: 2024-09-08 13:05:06 Age [y:d:h:m:s]: 00:122:16:42:58
Block: 1105650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87749 RingCT/type: yes/0
Extra: 01e8ec3100a908cdf183e3fa2dbf890fa9f5e11a79283ba9b36ba8d6db5d9f4055021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f50ef684bda9748702ef5ec3968bcffbf23f41e69aad71fd724bdddd84be1c8c 0.600000000000 1583055 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": 1105660, "vin": [ { "gen": { "height": 1105650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f50ef684bda9748702ef5ec3968bcffbf23f41e69aad71fd724bdddd84be1c8c" } } ], "extra": [ 1, 232, 236, 49, 0, 169, 8, 205, 241, 131, 227, 250, 45, 191, 137, 15, 169, 245, 225, 26, 121, 40, 59, 169, 179, 107, 168, 214, 219, 93, 159, 64, 85, 2, 17, 0, 0, 0, 4, 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