Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 933c961bb18bfcedc3d06325b774917d03f340870f3a604b5c751d6087281fee

Tx prefix hash: 1e00f3a7bddc9b3a586544017b57c3afe3ffa8f481c20181a630585ed8e714ea
Tx public key: 63626bbd95dc29f0da6259a8ef9c512fa9f14725162e6becb55cf9161124204c
Timestamp: 1746262124 Timestamp [UCT]: 2025-05-03 08:48:44 Age [y:d:h:m:s]: 00:196:11:59:42
Block: 1274765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138142 RingCT/type: yes/0
Extra: 0163626bbd95dc29f0da6259a8ef9c512fa9f14725162e6becb55cf9161124204c02110000000b9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0e4d562b7f721c8af83132dcc1f6a84f568614782a22f031d3dd6cf116c769f 0.600000000000 1762064 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": 1274775, "vin": [ { "gen": { "height": 1274765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0e4d562b7f721c8af83132dcc1f6a84f568614782a22f031d3dd6cf116c769f" } } ], "extra": [ 1, 99, 98, 107, 189, 149, 220, 41, 240, 218, 98, 89, 168, 239, 156, 81, 47, 169, 241, 71, 37, 22, 46, 107, 236, 181, 92, 249, 22, 17, 36, 32, 76, 2, 17, 0, 0, 0, 11, 159, 159, 230, 140, 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