Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 634f120a3ae2faf0927d2572238eef43e275d1a3dead218bb06cdc93fe78a56c

Tx prefix hash: e8f3bb2711e8d834853364042065c27fc3b885b4d6d4f1122e0a619b295deaa3
Tx public key: 0165b450c7449eadbdf419312a51782a157f9962317f6f7f27a868c89c6837e5
Timestamp: 1735953610 Timestamp [UCT]: 2025-01-04 01:20:10 Age [y:d:h:m:s]: 00:306:00:30:43
Block: 1189687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216194 RingCT/type: yes/0
Extra: 010165b450c7449eadbdf419312a51782a157f9962317f6f7f27a868c89c6837e50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00a3ceab927802f7eb7b846809439d75a6d588b340f81e9fa5da91744e47aafd 0.600000000000 1676198 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": 1189697, "vin": [ { "gen": { "height": 1189687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a3ceab927802f7eb7b846809439d75a6d588b340f81e9fa5da91744e47aafd" } } ], "extra": [ 1, 1, 101, 180, 80, 199, 68, 158, 173, 189, 244, 25, 49, 42, 81, 120, 42, 21, 127, 153, 98, 49, 127, 111, 127, 39, 168, 104, 200, 156, 104, 55, 229, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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