Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94be2f6f9e565e9bce0269c1289d16fbfa8128770c848de8610ec43ae85b9fc8

Tx prefix hash: 4c008f4b20114ead7d7db1b65ce3e112ae2f8aacbeffe1884b0f63f415cb6a1d
Tx public key: 26cc05bf749b4b957882a6f1620c0f9d8d3eb7a2441ee2d59ffa84787f65f4e9
Timestamp: 1763659020 Timestamp [UCT]: 2025-11-20 17:17:00 Age [y:d:h:m:s]: 00:048:21:16:55
Block: 1416375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35020 RingCT/type: yes/0
Extra: 0126cc05bf749b4b957882a6f1620c0f9d8d3eb7a2441ee2d59ffa84787f65f4e902110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bb11f665432d64e71d197a823d0bddaa4741caab985be5bf06bb755099328c9 0.600000000000 1904894 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": 1416385, "vin": [ { "gen": { "height": 1416375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bb11f665432d64e71d197a823d0bddaa4741caab985be5bf06bb755099328c9" } } ], "extra": [ 1, 38, 204, 5, 191, 116, 155, 75, 149, 120, 130, 166, 241, 98, 12, 15, 157, 141, 62, 183, 162, 68, 30, 226, 213, 159, 250, 132, 120, 127, 101, 244, 233, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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