Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25fcbac99f0c49b81c5e2f3f2b30a0752a0a262ff488b538e6cf1a084d2bae91

Tx prefix hash: 665d8f26d75505a89768a63ff5c6e0f31a28c4660dc386fa7c50c31aec1e5842
Tx public key: ecfe2f3978c702bb7687c26c019286726d1a4d67b56e6211a941bf74753793e0
Timestamp: 1712205637 Timestamp [UCT]: 2024-04-04 04:40:37 Age [y:d:h:m:s]: 01:059:23:04:18
Block: 992911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303879 RingCT/type: yes/0
Extra: 01ecfe2f3978c702bb7687c26c019286726d1a4d67b56e6211a941bf74753793e00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fa53fb44bc407af8479a98b4b16b16cf75c5ad4751d618d6a09387c825eebb9 0.600000000000 1453289 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": 992921, "vin": [ { "gen": { "height": 992911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fa53fb44bc407af8479a98b4b16b16cf75c5ad4751d618d6a09387c825eebb9" } } ], "extra": [ 1, 236, 254, 47, 57, 120, 199, 2, 187, 118, 135, 194, 108, 1, 146, 134, 114, 109, 26, 77, 103, 181, 110, 98, 17, 169, 65, 191, 116, 117, 55, 147, 224, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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