Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da85c2f3ce2937c56d78955dab5ac177e91cc17b0ace5e8547a3ee8560f117db

Tx prefix hash: fc779b22b0847653a66cfda4f4a9d92a3fa2cf0824a06afe4cf381ae6916f7c6
Tx public key: a0db7c926525be5a661e44eaddb17d276c5b333c5cbdc1ef2c60ab2db22ff98f
Timestamp: 1728574534 Timestamp [UCT]: 2024-10-10 15:35:34 Age [y:d:h:m:s]: 00:233:20:17:11
Block: 1128640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166966 RingCT/type: yes/0
Extra: 01a0db7c926525be5a661e44eaddb17d276c5b333c5cbdc1ef2c60ab2db22ff98f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dec97b0f5ba009c0093f76afefa42937c6e6188b0a077abd8d07c01d850efa9 0.600000000000 1611459 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": 1128650, "vin": [ { "gen": { "height": 1128640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dec97b0f5ba009c0093f76afefa42937c6e6188b0a077abd8d07c01d850efa9" } } ], "extra": [ 1, 160, 219, 124, 146, 101, 37, 190, 90, 102, 30, 68, 234, 221, 177, 125, 39, 108, 91, 51, 60, 92, 189, 193, 239, 44, 96, 171, 45, 178, 47, 249, 143, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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