Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0d13812a27bbfdd40d81cf1aa5abab42d72d59c976fc343c041c4937f7eb921

Tx prefix hash: b4b684dcff2011529a4582d521633ee378684c584a198d6da114b7e75fc3a01a
Tx public key: 93a6bac1da4e36e00a34de4c9d0f833db7edda95de0ee83f71ee1a1d7821f122
Timestamp: 1764214357 Timestamp [UCT]: 2025-11-27 03:32:37 Age [y:d:h:m:s]: 00:011:01:32:12
Block: 1420987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7919 RingCT/type: yes/0
Extra: 0193a6bac1da4e36e00a34de4c9d0f833db7edda95de0ee83f71ee1a1d7821f122021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0bd0eb82c9aa142810ceda52085654926ff2e3d997b5812ef251ce6209fb622 0.600000000000 1909542 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": 1420997, "vin": [ { "gen": { "height": 1420987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0bd0eb82c9aa142810ceda52085654926ff2e3d997b5812ef251ce6209fb622" } } ], "extra": [ 1, 147, 166, 186, 193, 218, 78, 54, 224, 10, 52, 222, 76, 157, 15, 131, 61, 183, 237, 218, 149, 222, 14, 232, 63, 113, 238, 26, 29, 120, 33, 241, 34, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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